From: Stan Shebs <shebs@apple.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com,
Andrew Cagney <ac131313@cygnus.com>,
"David S. Miller" <davem@redhat.com>
Subject: Re: which patches to review
Date: Fri, 26 Apr 2002 09:26:00 -0000 [thread overview]
Message-ID: <3CC97FB8.BE4F0369@apple.com> (raw)
In-Reply-To: <20020425214551.A12948@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Thu, Apr 25, 2002 at 09:36:11PM -0400, Christopher Faylor wrote:
> >
> > Hmm. I was under the impression that 1) Andrew was the head maintainer
> > for gdb
>
> If so, this isn't said anywhere. It certainly may be true; all I know
> is that he's a blanket write maintainer and the release manager for the
> last several releases. If the GDB projects has a single head
> maintainer, perhaps that should be listed in gdb/MAINTAINERS somewhere?
The old situation was that from the point of view of the FSF, I
was the sole maintainer, and that everybody else was at most
"helpers" (I kid you not). After the formation of the GDB
Steering Committee - which was never announced by RMS like he
was supposed to - I proposed to the committee that I retire
as maintainer, but that we retain the concept of a single
head or chief maintainer, mainly to avoid the evils of committee
indecisiveness, and that Andrew be that chief maintainer.
There was basically no reaction either positive or negative, not
exactly a ringing endorsement, but certainly justifying my
concern about the decisionmaking abilities of committees! :-)
So we've proceeded on that basis "unofficially" since then, and it
seems to have worked well enough. You're right that it ought to
be documented; I can do it if the head maintainer is shy about
taking the crown and putting it on his own head. :-)
Stan
next prev parent reply other threads:[~2002-04-26 16:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:49 David S. Miller
2002-04-23 7:47 ` Elena Zannoni
2002-04-23 7:54 ` Daniel Jacobowitz
2002-04-23 22:19 ` David S. Miller
2002-04-24 8:53 ` Stan Shebs
2002-04-24 10:16 ` Andrew Cagney
2002-04-24 10:48 ` David S. Miller
2002-04-24 12:16 ` Kevin Buettner
2002-04-24 12:25 ` David S. Miller
2002-04-25 7:04 ` Andrew Cagney
[not found] ` <mailpost.1019743470.13502@news-sj1-1>
2002-04-25 9:19 ` cgd
2002-04-25 7:32 ` Andrew Cagney
2002-04-25 18:04 ` David S. Miller
2002-04-25 20:27 ` Andrew Cagney
2002-04-25 18:14 ` Daniel Jacobowitz
2002-04-25 18:36 ` Christopher Faylor
2002-04-25 18:45 ` Daniel Jacobowitz
2002-04-25 19:17 ` Christopher Faylor
2002-04-25 20:33 ` Andrew Cagney
2002-04-26 9:26 ` Stan Shebs [this message]
2002-04-25 20:17 ` Andrew Cagney
2002-04-25 22:00 ` Daniel Jacobowitz
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=3CC97FB8.BE4F0369@apple.com \
--to=shebs@apple.com \
--cc=ac131313@cygnus.com \
--cc=davem@redhat.com \
--cc=drow@mvista.com \
--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