From mboxrd@z Thu Jan 1 00:00:00 1970 From: fche@redhat.com (Frank Ch. Eigler) To: Andrew Cagney Cc: Fernando Nasser , GDB Patches , fche@redhat.com Subject: Re: Write after approval additions Date: Fri, 09 Feb 2001 10:06:00 -0000 Message-id: References: <3A817ED7.60A7B32C@cygnus.com> <3A81AC7D.22AC2232@cygnus.com> X-SW-Source: 2001-02/msg00157.html cagney wrote: : [...] : Someone gets to add themselves to the write after : approval list of the MAINTAINERS file when they: : : o have recently demonstated an ability : to submit good quality patches to : gdb-patches. : (Hint, fix something trivial) : : o have an assignment in place : : o have OpenSSH and can reach the : repository (so an account can be : created). It may be instructive to contrast this policy with that of binutils: # --------- 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. - FChE