From: fche@redhat.com (Frank Ch. Eigler)
To: DJ Delorie <dj@redhat.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Write after approval additions
Date: Fri, 09 Feb 2001 12:35:00 -0000 [thread overview]
Message-ID: <o5r917zjau.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <xnhf23zoed.fsf@greed.delorie.com>
DJ Delorie <dj@redhat.com> writes:
: [...]
: There was *no* list of write-after-approval people for binutils. All
: I had to go on was the cvs permissions list and a long history of
: random people checking things in all over the place. [...]
Right, but if you need to police CVS commits after the fact, then you
have the same problem. In other words, the effects of
write-after-approval in the binutils vs gdb senses are hard to
distinguish: if someone checks in approved patches, there is no
problem in either case; if someone checks in unapproved patches, the
same badness occurs in both cases.
: > In what way is it a *useful* middle point between maintainers and
: > ordinary contributors?
: [...]
Sorry, I meant to wonder aloud about the spectrum between maintainers
and those potential contributors who already have CVS access, but are
not on the GDB list, or equivalently, between the gdb vs binutils
senses.
- FChE
next prev parent reply other threads:[~2001-02-09 12:35 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 [this message]
2001-02-13 13:55 ` Andrew Cagney
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=o5r917zjau.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=dj@redhat.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