On 26/03/2008, at 8:45 AM, Tim Chevalier wrote:
Is there a way to insulate myself from GHC breakage (and I realize
that in the HEAD, a certain amount of breakage is inevitable) while
still checking in my changes on a regular basis? I see two
alternatives:
1) commit my changes frequently, on a branch and merge it to the HEAD
at some future time (but past experience has shown that merging it
later is just too painful)
2) never commit my changes until I consider my work "done", then
commit them all at once (but it generally seems better to commit small
amounts of code often; plus, this has more or less the same problem
with merging)
Do other people have any thoughts/experiences related to this?
Cheers,
Tim
Use three different repos.
I have ghc-HEAD, ghc-HEAD-work and ghc-HEAD-test
you can copy them with something like
darcs get ghc-HEAD --repo-name=ghc-HEAD-work
Keep your ghc-HEAD synchronized with the one on haskell.org, do all
your hacking on ghc-HEAD-work, and push patches into ghc-HEAD-test to
validate and make sure you've added all your new files into darcs.
When you pull new patches into ghc-HEAD you can do a quick test build
there before pulling them into ghc-HEAD-work as well. If you break ghc-
HEAD-work you can make a new copy from ghc-HEAD and save the download.
If you have multiple cpus/cores you can leave validate running on ghc-
HEAD-test and still do your work in ghc-HEAD-work.
I would make sure to commit your changes as you go to ward against
patch conflicts.
Ben.
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
