commit-classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU indent for C code


From: Mark Wielaard
Subject: Re: GNU indent for C code
Date: Fri, 02 Apr 2004 18:02:04 +0200

Hi,

On Mon, 2004-03-29 at 02:09, Etienne Gagnon wrote:
> This is the greatest pitfall of the CVS single trunk of development approach;
> any change to the trunk potentially break all the other developer's code.
> 
> It is highly time to move development away from CVS.  What are the problems to
> do so *NOW*?  Political ones? e.g. GNU's savannah does not support it, so we
> won't do it?

Partially, yes. Savannah doesn't provide it yet so we also don't provide
it. The other reason of course is that CVS is much more well known then
any of the other version management systems. We don't want to introduce
extra barriers for people to hack on GNU Classpath.

That said I would love to experiment with monotone for distributed GNU
Classpath development across projects. But time is always a factor.

> I don't care
> whether it's hosted on savannah or not; the development site should be hosted
> in the best way for the project as a whole.

Since Savannah is the central point for development, distribution and
maintenance of GNU Software it is natural for GNU Classpath to be hosted
there. And I think this is better for the project as a whole (whether
you see that as the GNU project or just GNU Classpath). Savannah is
sponsored by the FSF which means there are people keeping it up to date
and fixing issues with it. Paul Fisher (one of the original founders if
GNU Classpath!) is now employed by the FSF to improve savannah. He sends
weekly status updates to the savannah-hackers mailinglist. If you want
to make subversion or any other improvement to savannah happen please
hop on the address@hidden mailing list. I think they would
love to add support for other ways for Free Software hackers to
collaborate.

Cheers,

MArk

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]