This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Patch: pacth for score backend document and code
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Rask Ingemann Lambertsen <rask at sygehus dot dk>
- Cc: liqin at sunnorth dot com dot cn, Mike Stump <mrs at apple dot com>, gcc at gcc dot gnu dot org, Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>, richard at codesourcery dot com
- Date: Thu, 26 Oct 2006 14:10:52 -0700
- Subject: Re: Patch: pacth for score backend document and code
- References: <5BB7AA9B-D561-42D2-A958-320C7755D01E@apple.com> <OF58E6AACA.78AFD68F-ON48257211.00099D0A-48257211.0012E008@sunnorth.com.cn> <87mz7jb65k.fsf@talisman.home> <20061026194957.GS24007@sygehus.dk>
On Thu, Oct 26, 2006 at 09:49:57PM +0200, Rask Ingemann Lambertsen wrote:
> On Thu, Oct 26, 2006 at 01:41:59PM +0100, Richard Sandiford wrote:
> > More important (and getting off the soap-box, or at least changing to a
> > different one): people seem to be saying that Liqin acted wrongly in
> > checking in patches to the port. Surely the procedural problem was
> > at the FSF end: a global maintainer gave permission for something to
> > be added before any maintainer had been appointed for it.
>
> I can't find the place that says that a maintainer has to be appointed
> for a new backend before its inclusion in GCC.
>
> I can't find the place that describes the procedure for appointing
> maintainers. Not having this clearly documentaion will easily cause
> confusion because people who are not maintainers but have "write after
> approval" permission are also listed in a file called MAINTAINERS, where
> they are even supposed to add themselves.
The Steering Committee appoints maintainers, and must approve new ports,
language front ends, and the like.
Once a maintainer is appointed, someone on the SC will ask the maintainer
to add him/herself to MAINTAINERS.