| Regardless, I can take care of it from here.
great. But I could not validate because of this, so may not be finished.
Would it make sense to push changes to the haddock repo (as I have done for my other inflight changes)?
Anyway, if you'd like me to take this any further, let me know explicitly, with instructions for how to build.
Thakns
Simon
| -----Original Message-----
| From: Ben Gamari [mailto:ben@well-typed.com]
| Sent: 26 October 2015 18:56
| To: Simon Peyton Jones
| Cc: ghc-devs@haskell.org
| Subject: Re: can't get haddock patch
|
| Simon Peyton Jones writes:
|
| > Ben
| > What does this mean? (below) Does it mean you have not pushed something
| to the haddock repo>
| > This happens when I'm on branch wip/T9858-typeable-ben2, in the main
| repo
| >
| > Simon
| >
| > git submodule update
| >
| > fatal: reference is not a tree: 289ef817aad02c341beb6d4c28ba0495872f5a0f
| >
| This means that the commit listed doesn't appear to be a commit in the
| `haddock` repository.
|
| I suspect I forgot to point out that the haddock changes are available
| in my Haddock repository on Github [1]. You would have needed to do
| something like this to see them,
|
| $ cd utils/haddock
| $ git remote add bgamari git://github.com/bgamari/haddock
| $ git remote update
|
| At which point you would have commit in question and could try `git
| submodule update` again.
|
| Regardless, I can take care of it from here.
|
| Cheers,
|
| - Ben
|
|
| [1] https://github.com/bgamari/haddock/tree/T9858
