public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Bernd Schmidt <bernds@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: MAINTAINERS policy question
Date: Sun, 16 Sep 2001 03:12:00 -0000	[thread overview]
Message-ID: <u8k7yz78nk.fsf@gromit.moeb> (raw)
In-Reply-To: <Pine.LNX.4.33.0109161049050.4907-100000@host140.cambridge.redhat.com>

Bernd Schmidt <bernds@redhat.com> writes:

> I have a question about how the MAINTAINERS file should be interpreted.
> Suppose you have somebody listed as maintaining port X.  Does this grant
> the right to check in any patch for a problem that affects port X, or
> does it only grant the right to modify config/X/*?
>
> I've had someone claim in private mail that it means the former, and
> this surprised me, since I always assumed it meant the latter.

The MAINTAINERS file states:

  Note individuals who maintain parts of the compiler need approval to
  check in changes outside of the parts of the compiler they maintain.

The cvswrite.html page states under "Write access policies":
   Localized write permission.
          This is for people who have primary responsibility for ports,
          front ends, or significant hunks of code in the compiler. These
          folks are allowed to make changes in code they maintain without
          going through any kind of approval process.

I interpret this so that if somebody maintains port X it only gives
check-in rights for config/X/*,

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2001-09-16  3:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-16  2:52 Bernd Schmidt
2001-09-16  3:12 ` Andreas Jaeger [this message]
2001-09-16  3:38   ` Graham Stott
2001-09-16 10:59   ` Mark Mitchell
2001-09-16 11:16     ` Andreas Jaeger
2001-09-16 11:17       ` Mark Mitchell
2001-09-16 11:22         ` Toon Moene
2001-09-16 11:23       ` Gerald Pfeifer
2001-09-16 14:14     ` David Edelsohn
2001-09-17  8:32       ` Phil Edwards
2001-09-16  4:06 ` Joseph S. Myers
2001-09-16 15:04 ` Joe Buck
2001-09-16  6:04 Ulrich Weigand
2001-09-16 18:19 ` DJ Delorie
2001-09-16  6:39 Richard Kenner
2001-09-16  8:35 ` Daniel Berlin
2001-09-16  8:38 Richard Kenner
2001-09-16 11:46 Richard Kenner
2001-09-16 12:24 ` Andreas Jaeger
2001-09-17  9:44 Ulrich Weigand
2001-09-17 17:40 mike stump
2001-09-18 16:30 ` Marc Espie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u8k7yz78nk.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=bernds@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).