This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Write after approval additions
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Subject: Re: Write after approval additions
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Tue, 13 Feb 2001 14:10:28 -0500
- Cc: Andrew Cagney <cagney at cygnus dot com>, Fernando Nasser <fnasser at cygnus dot com>, GDB Patches <gdb-patches at sourceware dot cygnus dot com>
- References: <3A817ED7.60A7B32C@cygnus.com> <3A81AC7D.22AC2232@cygnus.com> <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