[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Version control requirements for GCC

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2004-06-09 20:32:19 CEST

kfogel@collab.net wrote:

> Garrett Rooney <rooneg@electricjellyfish.net> writes:
>>>In case nobody but ghudson and me noticed, the GCC project is (again)
>>>looking for something that would replace CVS. Here's the initial post
>>>and thread:
>>> http://gcc.gnu.org/ml/gcc/2004-06/msg00264.html
>>>I think we should follow this more closely. We'd have to add a few
>>>features to cover most of this list, but I think that getting the GCC
>>>repository to move to Subversion would be a huge win.
>>Damn, that's a long list of requirements they've got there...
> I doubt they're going to find anything that meets all the
> requirements, which means they'll have to drop some eventually.

Yeah, there were some things on their list where I don't know /any/
system that supports it, and no system seems to hit all the high points

> The emphasis on disconnected commits is a bit surprising. They're
> useful, I just didn't realize they were *that* useful for this
> particular development team.

Well, they mention 'disconnected development', and say that some systems
provide disconnected commits and some don't. I didn't get the
impression that it was a hard requirement.

> (I wonder if Ian considered svk.)

It was mentioned in one of the follow up posts, but I don't think it was
really considered a serious contender at this point.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 9 20:32:59 2004

This is an archived mail posted to the Subversion Dev mailing list.