From: Andrew Cagney <ac131313@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Andrew Cagney <cagney@cygnus.com>,
Fernando Nasser <fnasser@cygnus.com>,
GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: Write after approval additions
Date: Tue, 13 Feb 2001 13:55:00 -0000 [thread overview]
Message-ID: <3A8986A4.783810A6@cygnus.com> (raw)
In-Reply-To: <o51yt720k1.fsf@toenail.toronto.redhat.com>
"Frank Ch. Eigler" wrote:
> # --------- Write After Approval ---------
> #
> # Individuals with "write after approval" have the ability to check in
> # changes, but they must get approval for each change from someone in
> # one of the above lists (blanket write or maintainers).
> #
> # [It's a huge list, folks. You know who you are. If you have the
> # *ability* to do binutils checkins, you're in this group. Just remember
> # to get approval before checking anything in.]
>
> I've always wondered what this specific colour along the power
> spectrum was supposed to accomplish. In what way is it a *useful*
> middle point between maintainers and ordinary contributors?
>
> It has the unintended consequence of making more work for maintainers.
> They have to check in approved patches themselves instead of letting a
> contributor do it.
Kind of :-)
Once someones name is in the MAINTAINERS file the people giving approval
can be sure of the above all hold. Significantly, they can be sure that
the person has a valid assignment.
To turn the question around, how to BFD maintainers know if someone
submitting a patch has a valid GDB assignment in place?
Andrew
next prev parent reply other threads:[~2001-02-13 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A817ED7.60A7B32C@cygnus.com>
[not found] ` <3A81AC7D.22AC2232@cygnus.com>
2001-02-09 10:06 ` Frank Ch. Eigler
2001-02-09 11:01 ` DJ Delorie
2001-02-09 12:35 ` Frank Ch. Eigler
2001-02-13 13:55 ` Andrew Cagney [this message]
2001-02-14 4:24 ` Frank Ch. Eigler
2001-02-14 7:50 ` Andrew Cagney
2001-02-14 7:54 ` Frank Ch. Eigler
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=3A8986A4.783810A6@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cagney@cygnus.com \
--cc=fche@redhat.com \
--cc=fnasser@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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