Git v. Darcs: megapatches and 'darcs shunt'
haskell.vivian.mcphail at gmail.com
Wed Jan 12 08:52:17 CET 2011
I have a couple of branches of ghc off of HEAD.
I found that I had some difficulty _finding_ my patch submissions after
weeks of 'darcs_all pull -a'. And I understand that one complaint is the
need to create 'megapatches'.
How is this flow:
1) 'darcs shunt' all patches originating from this repository to a waiting
2) 'darcs pull' new patches from GHC HQ
3) 'darcs unshunt' from a holding area onto the updated repo
Essentially we do not discard patches as with 'unrecord', instead we create
a sub-branch and reapply each patch (with conflict resolution).
If I were to have a say, I would stay with darcs, but as someone has pointed
out, the technology is the compiler, not the VCS.
This transmission contains information that may be confidential. It is
intended for the named addressee only. Unless you are the named addressee
you may not copy or use it or disclose it to anyone else.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cvs-ghc