Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] Add add_setshow_enum_cmd, use in mips
Date: Mon, 01 Nov 2004 22:37:00 -0000	[thread overview]
Message-ID: <20041101223716.GB28889@nevyn.them.org> (raw)
In-Reply-To: <01c4c057$Blat.v2.2.2$4cacd760@zahav.net.il>

On Mon, Nov 01, 2004 at 11:09:51PM +0200, Eli Zaretskii wrote:
> > Date: Mon, 1 Nov 2004 00:12:57 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
> > 
> > There is no maintainer for this area, and Andrew is entitled to
> > approve patches himself, so an RFA (request for approval) seems
> > unnecessary.
> 
> Where do you see such a rule?  It's not in MAINTAINERS, AFAICT.
> 
> The rule that we do have is that if a certain maintenance area has no
> responsible maintainer, the _responsibility_ falls to the head
> maintainer.

No, we don't have any rule like that.  If a certain area has no
maintainers, the responsibility falls to the global maintainers - all
of us.

>  But my interpretation of this is that the responsibility
> is for reviewing patches, not for applying own patches without asking
> for approval.  That's because it doesn't make sense to me to decide
> that whenever some area maintainer steps down, the head maintainer is
> automatically promoted to be an expert in that area.  If you were not
> an expert in some area, the fact that the expert disappeared doesn't
> make you an expert, just the one who is burdened with more duties.

If there were an expert, who cared enough to disagree with any patches
applied, perhaps that person should be maintaining said area.  I only
see a point for maintainers to post RFAs when (A) they can not approve
the patch themselves or (B) they are not confident/happy/sure with the
approach.  We don't operate on consensus (obviously enough from reading
the lists).

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-11-01 22:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 17:11 Andrew Cagney
2004-10-30 23:24 ` Eli Zaretskii
2004-10-31 23:01   ` Andrew Cagney
2004-11-01  4:47     ` Eli Zaretskii
2004-11-01  5:12       ` Daniel Jacobowitz
2004-11-01 21:15         ` Eli Zaretskii
2004-11-01 22:37           ` Daniel Jacobowitz [this message]
2004-11-02  4:51             ` Eli Zaretskii
2004-11-09  1:15               ` Daniel Jacobowitz
2004-11-09  5:00                 ` Eli Zaretskii
2004-11-09 15:29                   ` Andrew Cagney
2004-11-09 18:42                     ` Daniel Jacobowitz
2004-11-10  4:33                       ` Eli Zaretskii
2004-11-10 20:55                         ` Eli Zaretskii
2004-11-10 21:42                           ` Mark Kettenis
2004-11-10 23:31                             ` Eli Zaretskii
2004-11-10 23:41                               ` Daniel Jacobowitz
2004-11-11  0:00                                 ` Eli Zaretskii
2004-11-11  5:37                                   ` Daniel Jacobowitz
2004-11-11  5:59                                     ` Joel Brobecker

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=20041101223716.GB28889@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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