Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, RaoulGough@yahoo.co.uk
Subject: Re: coffread.c extension for DLLs without debugging symbols
Date: Sat, 04 Jan 2003 16:42:00 -0000	[thread overview]
Message-ID: <200301041641.h04Gft101583@duracef.shout.net> (raw)

Hi Raoul,

> What does RFA stand for? Seemed to me like it was used by people who
> were actually capable of updating the CVS themselves and just wanted
> confirmation.

"RFA" == "Request for Approval".

GDB has a human approval system that goes beyond the CVS permissions.
You can read about it in the top level MAINTAINERS file.

There are three levels of access.  'Blanket Maintainers' have the
authority to commit files anywhere in the gdb tree.  Several types
of 'Maintainers' have authority to commit files in their area of
responsibility.  'Write After Approval' maintainers have the authority
to commit their patches if a Blanket Maintainer or a Maintainer approves
them.

All of these people have write permission in the CVS repository.
If someone exceeds their authority and commits a patch without the
necessary authority, then the Head Maintainer would deal with them
and with their unauthorized commit.  This does not happen very often.

Many maintainers, even Blanket Maintainers, ask for RFA on patches
that they have the authority to commit.  If there is an active
Maintainer for an area, it's a smart move to get the Maintainer's
opinion before commiting to that area.

Other request types are:

  RFC == "request for comments".  The submitter wants feedback on the
  patch and may not even want to commit it yet.

  RFA == "request for approval".  The submitter has little doubt that
  the patch is ready to commit, and just wants a short answer.

  PATCH == "it's going in".  The submitter has authority to commit
  this patch and is about to do so, either immediately or as soon as
  they get around to it.  No reply is needed.

Michael Snyder knows the nuances of this system better than I do;
he may have some corrections.

I just filed a PR to document this stuff for the benefit of first-time
patch writers.

Michael C


             reply	other threads:[~2003-01-04 16:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 16:42 Michael Elizabeth Chastain [this message]
2003-01-05 15:40 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03 19:41 Raoul Gough
2003-01-04  0:53 ` Michael Snyder
2003-01-04  4:43 ` Christopher Faylor
2003-01-04 16:31   ` Raoul Gough
2003-01-04 17:54     ` Eli Zaretskii
2003-01-04 20:51     ` Christopher Faylor
2003-01-05 14:44       ` Mark Kettenis
2003-01-05 17:18         ` Christopher Faylor
2003-01-05 17:40           ` Daniel Jacobowitz
2003-01-07  1:03       ` Raoul Gough
2003-01-07  1:12         ` Daniel Jacobowitz
2003-01-07 13:11       ` Raoul Gough
2003-01-07 16:46         ` Christopher Faylor
2003-01-07  2:28     ` Michael Snyder
2003-01-07  2:24   ` Michael Snyder
2003-01-04 11:03 ` Eli Zaretskii
2003-01-04 16:21   ` Raoul Gough
2003-01-06 17:10   ` Elena Zannoni
2003-01-06 17:41     ` Christopher Faylor
2003-01-07  0:46     ` Raoul Gough
2003-01-07  1:53       ` Elena Zannoni
2003-01-10 22:45         ` Raoul Gough
2003-01-07  1:00     ` Andrew Cagney
2003-01-10 22:37       ` Raoul Gough

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=200301041641.h04Gft101583@duracef.shout.net \
    --to=mec@shout.net \
    --cc=RaoulGough@yahoo.co.uk \
    --cc=gdb-patches@sources.redhat.com \
    /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