This is the mail archive of the
mailing list for the GCC project.
3.5 integration branch created
- From: Geoffrey Keating <geoffk at apple dot com>
- To: "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Cc: Caroline Tice <ctice at apple dot com>
- Date: Tue, 13 Jan 2004 17:14:05 -0800
- Subject: 3.5 integration branch created
I have created the gcc-3.5-integration-branch. It is similar in some
ways to the 'basic-improvement' branch in the GCC 3.4 timeframe, but
has some significant differences. The rules for the branch are:
1. This branch is for fully-tested, approved patches. The rules for
committing to it are the same as the rules that apply during Stage 1 of
GCC development. Experimental or incomplete work should not be put on
2. The intention is that immediately after GCC 3.4 branches, this
branch will be merged back to mainline.
3. I will be making regular (probably weekly) merges from mainline onto
this branch. I will be testing these merges with a powerpc-darwin
native bootstrap. Anyone who commits anything to the branch that can't
be fully tested with a powerpc-darwin native bootstrap should watch for
the mail I send out saying the merge is done, and then run a test on
their own platform and send the results to gcc-testresults.
4. Anyone who commits to the branch is still responsible for
maintaining the patch on the branch: fixing regressions that it causes,
and sometimes updating or reintegrating it after merges. I expect that
for most patches, this will be much less work than maintaining the
patch on their own.
5. I may back a patch out of the branch if it (a) causes bootstrap
failure or significant regressions on any platform and the author
doesn't appear to be able to fix it quickly, or (b) don't appear to
have followed Rule 1 or Rule 3.
I'll update the web pages tomorrow...
Description: S/MIME cryptographic signature