Hi,

One feature I *really* miss in darcs from svk/svn (which I'm stuck
with for some projects) is copying...

The ability to take some code, and duplicate it makes annotation
easier and more effective when you create derived copies.

In my current work on Catalyst in the perl community i've taken lots
of code, made a copy, and then transformed it - we needed a bunch of
reboots for some plugins, which included a different API, but some
shared code.

Some people might also like the trunk/branches/tags topology, and it
might be nice to support it for those people when they work with a
more central darcs repository. Maintaining darcs style tags has a
certain overhead, because it isn't easily browsable on the web
without duplicating a repo per fork.

Lastly, this should also ease migration from SVN.

-- 
 ()  Yuval Kogman <[EMAIL PROTECTED]> 0xEBD27418  perl hacker &
 /\  kung foo master: MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM: neeyah!

Attachment: pgpKJff4kIRmH.pgp
Description: PGP signature

_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users

Reply via email to