[darcs-users] use case showing DARCS's unique features?

[Zooko]

This message is a response to:
http://www.abridgegame.org/pipermail/darcs-users/2003/000143.html

 David Roundy wrote:
>
> Patch A: add file foo to repo
> B: modify file foo
> C: modify file bar (already existing before this scenario starts)

Very interesting!

To avoid confusion with the issue of metadata, we could rewrite this use case 
to have only one file:

Already existing before this scenario starts is a file that is only one 
line long.  The line is: "#!/usr/bin/runhugs".

Patch A: Add these four lines to the file:

"""

main =
    do
    print "hello world!"
"""

Patch B: change the last line of the file from 'print "hello world!"' to 
'print "yellow whirled!"'.

Patch C: change the first line of the file from "#!/usr/bin/runhugs" to 
"#!/usr/bin/env runhugs".

Now if I start with the original version of the file, and I ask my revision 
control system to pull patch B, I want the RCS to say "Patch B depends on 
Patch A.".  If I ask it to pull patch A or patch C, I want it to just do it.

So you say that DARCS will do this for me and that arch won't?

Very interesting!

Regards,

Zooko

http://zooko.com/
         ^-- under re-construction: some new stuff, some broken links