Good points, Stephen. On Sun, Apr 12, 2009 at 02:07:50 +0900, Stephen J. Turnbull wrote: > > * Amazing patch management. You commit patch A then B then C. You decide > > to modify or delete A. Other SCMs say "no can do". Darcs says "no > problem!".
So I don't want to turn this thread into a darcs-vs-git affair. My desire is to try and help us refine our thinking about marketing. At the risk of preaching to the choir, I decided to run this example from Jason's Master's Thesis, the idea I'm hoping to convey being that precision is important not just because of what it lets you do cleanly, but because of what misleading things it lets you avoid. I guess it would be hard to communicate this clearly though... The idea is that we want to merge a file swap change with a change that modifies one of the files. Does the right thing happen? I think Zooko may have had an example like this too... I guess what I'm trying to say is that it may make sense to think in terms of precision, and not just in terms of flexibility. mkdir gitstuff cd gitstuff git init touch x y git add x y git commit -m 'initial version' cd .. git clone gitstuff gitstuff2 cd gitstuff2 echo foo > y git add y git commit -m 'add something to y' cd .. cd gitstuff git mv x tmp git commit -m 'swap x/y step 1' git mv y x git mv tmp y git commit -m 'swap x/y step 2' git pull ../gitstuff2 cat y # err, shouldn't these changes be in x? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpOByAUvGfP6.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
