[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: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2004-06-10 16:43:07 CEST

On Jun 9, 2004, at 1:07 PM, 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.

Well of course, but we can dream, can't we :)

>
> 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.

We are a weird bunch :)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 10 17:02:51 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.