> I agree the support for composition isn't great (yet), but Subversion is
> being actively worked on and it will get there. For me, the compelling
> features of Subversion over CVS are the atomic commits and the fact that
> it can manage directories, copies and moves properly. I always hated
> the fact that if I wanted to move things around in CVS I had to actually
> muck about in the repository (and then lost the history, and couldn't
> reconstruct an old version - VSS also has this problem).
> If you are currently a VSS shop and are moving to something else, I
> would seriously recommend you don't shift to CVS now. Either make the
> shift to Subversion now and live with the poor composition support until
> it gets better, or wait and make the shift once it is supported.
> Otherwise you'll have to disrupt all the developers again once you shift
> from CVS to Subversion.
> Alternatively, you could shift now and help get the composition support
> added - it's open source, after all. That's how svncopy.pl got
> developed - it was hurting us so I wrote the script and submitted it.
> BTW I have no attachment to Subversion other than using it (mostly
Certainly I've got a bit of a tough decision here. We need to get off
of vss, and I am trying to head off the 'solution' of upgrading to vss
2005, which I am trying to do by presenting a compelling open-source
alternative. Unfortunately, the requirements are a bit steep compared
to svn's current capabilities and can be better met with cvs
(certainly there will be the move/copy/rename issue with cvs, but it
can be largely avoided). I would really like to see svn mature to
providing a superset of the functionality of cvs, so perhaps this is
all adding up to me pitching in ;) If the projected timeframe for
getting full composition support in svn is workable from our
perspective, maybe there is some middle ground where we could hobble
along with svn until then, perhaps assisted by tools like your
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Sep 30 13:23:16 2004