GCC Status Report (2004-03-21)

[Hans-Peter Nilsson]

> Date: Sun, 21 Mar 2004 12:27:28 -0800
> From: Mark Mitchell <mark@codesourcery.com>

> Henceforth, please do not make any non-documentation check-ins to the
> 3.4 branch without my explicit approval.  To get that approval, please
> do *not* send me mail directly.  Instead, add your patch to the
> relevant PR, which must be targeted at 3.r, and add me to the CC list
> for the PR.  Note that this procedure implies that if there is no PR
> targeted at 3.4 I will not accept the patch.
> 
> Furthermore, please do not create any new PRs targeted for 3.4 without
> my explicit permission.  If it's a regression, target it for 3.4.1.
> If you think it might need to be fixed in 3.4, add me to the CC list,
> and add a note asking me to move back the target.  Please do not do
> this unless the PR is wrong-code, ICE-on-valid, or bootstrap for a
> primary target.  New PRs referring to other categories of error are
> simply not going to get fixed for 3.4.

Sounds like I made a boo-boo when I created PR target/14676,
then (it's targeted at 3.4.0): libstdc++-v3 broke for cris-*
when massive changes including bugs were imported from main
trunk.  Due to branch restrictions I can't have it trivially
fixed for 3.4.0 because it's not bootstrap on a primary target?
I must be misunderstanding.  Oh well, I moved the target to
3.4.1 as per instructions.  Can't say *I* don't play by the
rules.

On a more productive note, I really suggest trusting target
maintainers for target-local fixes like this.  Please?  Perhaps
even *explicitly* allowing non-regression target-local fixes, as
for the 3.3 branch.  Alternatively, please enforce the check-in
policies, only that'd be vastly less productive.

brgds, H-P