This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.1 Projects
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
- Cc: Mark Mitchell <mark at codesourcery dot com>, Nathanael Nerode <neroden at twcny dot rr dot com>, gcc at gcc dot gnu dot org
- Date: Sun, 27 Feb 2005 18:53:05 -0500
- Subject: Re: GCC 4.1 Projects
- References: <42225041.2070308@codesourcery.com> <20050227233821.GA23540@atrey.karlin.mff.cuni.cz>
>>>>> Zdenek Dvorak writes:
Zdenek> I must admit I have very bad feeling about the whole "4.1 Projects"
Zdenek> stuff. IMHO this over-organizes things. If people in general disagree
Zdenek> with the Nathan's changes, or if there are any reasons to think that
Zdenek> they are not tested enough or whatever when he submits them, of course
Zdenek> that is something else. But I don't think having just a single person
Zdenek> decide which patches may go in and which must wait, or even just judging
Zdenek> their importance, is a good idea.
Given the number of branches and major changes queued up for GCC
4.1, we need to coordinate the way that they are merged to try to avoid
too much breakage and disruption. Mark is the GCC Release Manager and he
has the authority to try to herd the cats and manage this process.
Separately, I do not see anything in Nathanael's patch that should
create a dependency requiring the delay to Stage 2. Maybe there is a
communication problem or misunderstanding. If there is a way to
accomodate Nathanael, we should.
I would appreciate if you and everyone else who have disagreements
with individual decisions would stop turning these into complaints about
the entire process. There is no perfect solution. I'm sure that we all
would be happy to consider constructive suggestions, but complaining about
the abstract concept of someone else having control or making decisions is
not helpful.
David