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

[Zooko]

I'm looking for a new revision control system to replace CVS.  I've put up a 
web page detailing what I've learned so far:

http://zooko.com/revision_control_quick_ref.html

I've read the manual.  I really like the basic theory of patches (patches are 
invertible, they are dependent iff they don't commute, and "parallel" patches 
can always be merged).  Actually I'm not sure I like that third part.

Anyway, although I like the mathemtical abstraction of the basic theory of 
patches, I don't understand how such an abstraction would actually be used in 
a tool, and I definitely don't understand what DARCS can actually do in 
practice that arch or Meta-CVS cannot.

Could someone please show me the simplest text file and the simplest branch 
and merge that I might actually want to do in practice, and that DARCS 
facilitate where arch or Meta-CVS would complicate?

Thanks!

Regards,

Zooko

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