On Fri, Feb 04, 2005 at 01:47:11PM -0500, Bryan Donlan wrote: > Nicholas Clark wrote: > >On Fri, Feb 04, 2005 at 06:07:33PM +0100, Ron Blaschke wrote: > > > >>Just curious. Are there any plans moving parrot to subversion?
> >so CVS is about 20% faster. Elapsed time seems to be all that matters here. > > > >Nicholas Clark > > > > Wouldn't an update, commit, or switch operation be far more common than > a fresh checkout? On Fri, Feb 04, 2005 at 11:30:25AM -0800, [EMAIL PROTECTED] wrote: > --- Bryan Donlan <[EMAIL PROTECTED]> wrote: > > Nicholas Clark wrote: > > > On Fri, Feb 04, 2005 at 06:07:33PM +0100, Ron Blaschke wrote: > > > > > >>Just curious. Are there any plans moving parrot to subversion? > > > > > > so CVS is about 20% faster. Elapsed time seems to be all that > > matters here. > > Is this that important compared to the pain of CVS when trying to > rename files, move directories, etc.? If you never have to do stuff Maybe I should have been more clear. One big historical problem with subversion about a year ago was that for large checkouts performance really sucked. (ie a factor of 10 or worse). That has clearly all been fixed now, so isn't an issue. That's what I was trying to demonstrate. On the other hand, I think a figure of "within 10% of CVS" was said back in those days, as a metric for when svn had got there, and based on that then *strictly* it hasn't yet. IIRC there were a couple of other criteria it was suggested that svn should meet, but I've forgotten what they are. > Further, since things like "diff" are run against a local cache with > CVS it lowers bandwidth usage considerably if many developers are on a > project. > > So unless there are advanced CVS features that are required that SVN > does not provide (and if the switch is easy enough), I'd cheerfully > recommend SVN over CVS any day. Likewise. I think it would be a worthwhile switch to make. I'm not sure if there are any "advanced features" in CVS that svn doesn't provide. Although the best bit about using svn for your repository is that then you throw away the svn client and use svk instead. Why stop at diff when making things work offline? :-) Nicholas Clark
