On Sun, February 25, 2007 7:32 pm, John Goerzen said: > I have encountered the darcs hanging problem before, but had been able > to design my practices such that it didn't bite me. > > Until now:
I just had the same problem, and I'm also looking at alternative systems because I just can't worry about waiting hours for patches to apply. > Mercurial appears to suffer from none of the Darcs hanging problems, > while at the same time enabling all of the core functionality I want > from Darcs: distributed operation, cheap branching, full granular > history across merges, and even cherrypicking. I took a quick look at the hg docs after reading your email. One thing I noticed, and I could be wrong, but it seems like hg needs a lot more command line options, and even specific revision info to do certain things like update and merge. One think I've become accustomed to with darcs is recording patches with 'dev:' 'fix:' 'doc:' and prefixes like these, then going into another repo and doing 'darcs pull -p doc' and selecting the doc patches I want. That reminds me... darcs lets me y-or-n which changes to record as a patch. I assume the same effect in hg is achieved with separate repos for each patch being worked on? -- Jonathon McKitrick Reed Larkey Group _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
