This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Trunk frustration
- To: Stan Shebs <shebs at apple dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Subject: Re: Trunk frustration
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Wed, 25 Jul 2001 07:42:05 -0700
--On Monday, July 23, 2001 03:54:59 PM -0700 Stan Shebs <shebs@apple.com>
wrote:
> Am I the only one who's frustrated with the current state of the
> trunk?
I'm sure I would be too if I were working on the trunk right now.
The answer is that we now have a policy that gives us a mechanism for
returning to a known good state in a short period of time. However,
there are some checks and balances. So, you need to identify the
first patch that caused a regression that is still not fixed, notify
the instigator of that patch, and then get two people with write
privileges to agree to revert the patch if the problem is not fixed
within 48 hours.
If you can identify multiple problem-causing patches, you can do them
all at once!
And the answer is that, yes, this work probably should have been done
on a branch. It's goal seems to be to replace jump.c, which is great,
but seems to me roughly equivalent to creating a brand-new optimization
pass.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com