This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.4.0 Status Report (2009-03-13)
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, "bonzini at gnu dot org" <bonzini at gnu dot org>, "dave dot korn dot cygwin at googlemail dot com" <dave dot korn dot cygwin at googlemail dot com>, "dberlin at dberlin dot org" <dberlin at dberlin dot org>, "dje dot gcc at gmail dot com" <dje dot gcc at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "law at redhat dot com" <law at redhat dot com>, "mark at codesourcery dot com" <mark at codesourcery dot com>, "rguenther at suse dot de" <rguenther at suse dot de>, "stevenb dot gcc at gmail dot com" <stevenb dot gcc at gmail dot com>
- Date: Sun, 22 Mar 2009 23:38:54 -0700
- Subject: Re: GCC 4.4.0 Status Report (2009-03-13)
- References: <4aca3dc20903210608t1c27fc2ci440c69a22a19fcb8@mail.gmail.com> <303e1d290903211737u20100ed4ie0c604e2801517a2@mail.gmail.com> <49C58A77.3000805@codesourcery.com> <4aca3dc20903211937k29299a7co9bf4add50a050f71@mail.gmail.com> <20090322050024.GA18893@synopsys.com> <4aca3dc20903220547v8923d55v9ac593f8400be6a9@mail.gmail.com> <10903221258.AA04666@vlsi1.ultra.nyu.edu> <206fcf960903220718oefa452ek60dcc1d933e1e093@mail.gmail.com> <10903221441.AA05218@vlsi1.ultra.nyu.edu> <206fcf960903220808w4c04c0e9g74b25a55ea3d8b42@mail.gmail.com>
On Sun, Mar 22, 2009 at 08:08:38AM -0700, Gabriel Dos Reis wrote:
> It was my understanding that it was a compromise, but the
> EGCS community retains all rights to make technical
> decisions without disruptive interferences from FSF
And that's pretty much the way it's worked. RMS objected to using
bugzilla; we use bugzilla. RMS objected to switching to subversion.
RMS argued against independent administration of gcc.gnu.org.
RMS doesn't hang out on the gcc list trying to micromanage everything.
The maintainers are in charge of their areas; Mark and his team are
in charge of releases. And the day-to-day development practices
GCC uses are the ones developed in the egcs days. Remember the old
days when the location of the development tree and the snapshots was
a secret, and people were threatened with banning if they let it out?
I do think that RMS overstepped the line that we had set up when he
told us to hold off on creating a release branch. That was unprecedented
interference.