This is the mail archive of the
mailing list for the GCC project.
Re: r117771 - in /trunk: ChangeLog config.sub gcc/c...
- From: Ian Lance Taylor <iant at google dot com>
- To: liqin at sunnorth dot com dot cn
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: 18 Oct 2006 09:57:12 -0700
- Subject: Re: r117771 - in /trunk: ChangeLog config.sub gcc/c...
- References: <OFC14F3306.306DCD4A-ON4825720B.002F8DC1-4825720B.00313B00@sunnorth.com.cn>
> OK, I will post my patch to gcc-patches until you confirm my
> Wrire access policies.
As others have noted, the correct procedure is to always post all
patches to gcc-patches. If you are the maintainer for a target, you
do not need further approval for changes to code in config/TARGET.
But you still need to post the patch, and you still need to make a
> I had sent mail to email@example.com in Oct 11
> (also cc to Mark) to comfirm my Wrire access policies, but no response.
I'm not sure where you got the e-mail address root-owner. The correct
e-mail address for administrative questions is firstname.lastname@example.org.
You do have an account email@example.com, and you should be able to
However, you don't seem to be listed in MAINTAINERS. You should add
yourself to MAINTAINERS, with a ChangeLog entry.
The patch you sent removes an entry from ChangeLog for some reason
that I don't understand. That can only be correct if that change