Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [maint] New title for ``global write maintainer''?
Date: Thu, 07 Nov 2002 19:22:00 -0000	[thread overview]
Message-ID: <20021108032306.GB4502@nevyn.them.org> (raw)
In-Reply-To: <3DCAF816.8030403@redhat.com>

On Thu, Nov 07, 2002 at 06:32:38PM -0500, Andrew Cagney wrote:
> 
> >>The current ``global write maintainer'' title is something of a misnomer. 
> >>Unlike GCC, where a global write maintainer can an does approve any 
> >>patch, the GDB global write maintainers have an understanding that they 
> >>won't approve patches or directly make changes in areas where there is 
> >>already a maintainer.
> 
> 
> It actually reads ``blanket write privs'', which is a total misnomer.
> 
> >>Given the potential for confusion, I'm wondering anyone has a better 
> >>title?  The only one I've come up with so far is ``Council of Elders''(1) 
> >>but apparently some countries don't treat their elders with respect and, 
> >>hence, the term takes on less than plesant connitations :-(  Another 
> >>could be the Senate, ....
> 
> >
> >"default maintainer"?  "etc maintainer"? "all-that-other-code maintainer"? 
> >:-)
> 
> `Global Maintainer'?

I rather liked ``shmuck''.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-11-08  3:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3DB95391.10407@redhat.com>
2002-10-25  7:48 ` Andrew Cagney
2002-10-25 11:23   ` Stan Shebs
2002-10-25 14:35     ` Daniel Berlin
2002-11-07 15:32     ` Andrew Cagney
2002-11-07 19:22       ` Daniel Jacobowitz [this message]

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=20021108032306.GB4502@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@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