From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28978 invoked by alias); 1 Nov 2004 22:37:17 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28969 invoked from network); 1 Nov 2004 22:37:16 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 1 Nov 2004 22:37:16 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1COknc-0007YD-6E; Mon, 01 Nov 2004 17:37:16 -0500 Date: Mon, 01 Nov 2004 22:37:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: cagney@gnu.org, gdb-patches@sources.redhat.com Subject: Re: [commit] Add add_setshow_enum_cmd, use in mips Message-ID: <20041101223716.GB28889@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , cagney@gnu.org, gdb-patches@sources.redhat.com References: <4183BD22.3090905@gnu.org> <01c4bed6$Blat.v2.2.2$fa231b20@zahav.net.il> <41856ECA.2060701@gnu.org> <01c4bfcd$Blat.v2.2.2$299ef260@zahav.net.il> <20041101051257.GA11134@nevyn.them.org> <01c4c057$Blat.v2.2.2$4cacd760@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c4c057$Blat.v2.2.2$4cacd760@zahav.net.il> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-11/txt/msg00030.txt.bz2 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 > > Cc: Andrew Cagney , 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