Henri Yandell <[EMAIL PROTECTED]> writes: > > > On Tue, 4 Nov 2003, Justin Erenkrantz wrote: > > > --On Tuesday, November 04, 2003 23:16:50 +0000 Stephen Colebourne > > <[EMAIL PROTECTED]> wrote: > > > > > > > The one potential spanner in the works for me is subversion. When 99% of > > > the world uses CVS, I really struggle with this one. > > > > Have you tried Subversion? It really eases a lot of pain that CVS causes. > > Can I use a Subversion server with an existing CVS client? Some kind of > backwards compatibility bridge thing?
No, but you can convert your CVS repository to a Subversion repository using cvs2svn.py (Although it still has some issues with converting tags and branches, it can convert the trunk very nicely). I understand that this might be a problem, but Subversion's model doesn't map to CVS very well since Subversion has a lot of things that CVS doesn't (versioned directories, for one--for the whole list see http://subversion.tigris.org/). > > Renaming files is just so, gosh darn, beautiful; copying between projects > > is painless and cheap. That said, if using Subversion is the *only* > > bottleneck preventing a Jakarta Commons project from coming to the Apache > > Commons, I'd be fine with them still using CVS if they were a pre-existing > > project. > > Not only pre-existing projects on CVS though. If a new project is split > off of an existing project, it's not going to want to go and use > subversion. If developers from one of the CVS projects have a new idea, > they're not going to want to go and make those new ideas be in a > subversion project. I would prefer to poll developers rather than assume that all developers feel that way. -Fitz -- Brian W. Fitzpatrick <[EMAIL PROTECTED]> http://www.red-bean.com/fitz/
