On 18/05/2011 11:41, Karel Gardas wrote:
On 05/18/11 12:09 PM, Simon Marlow wrote:
The real difficulty with the ghc sources is that fact that
over a dozen different trees, with independant commit histories
are needed to retrieve a working revision.
Right, this is something that would be fixed by using submodules or
subtree merging.
If I understand well your arguments about submodules in the past, this
is something we will not see in the near future. However ability to grab
some known tree of the history would be great, for me too as I'm hit by
#5201, so I like Ben's suggestion of buildbots printing kind of tree
identification. Perhaps doing something like:
git log|head -1
inside the cloned tree for ghc git repo and also for all the git repos
got by sync-all is something which might help here a little bit and
should not be that hard to implement in builder server?
I just added a log command to sync-all, so you can now say
$ ./sync-all log HEAD^.. --pretty=oneline
to get the hashes of all the repos. I've added that to my nightly build
script too, when Ian returns he can add it to the main nightly builders.
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
