From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3946 invoked by alias); 19 Jan 2010 10:42:59 -0000 Received: (qmail 3937 invoked by uid 22791); 19 Jan 2010 10:42:58 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 19 Jan 2010 10:42:54 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 80F1F2BABFE; Tue, 19 Jan 2010 05:42:52 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Oplnd8woZFxY; Tue, 19 Jan 2010 05:42:52 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id DE9582BAB7F; Tue, 19 Jan 2010 05:42:51 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id DBA2CF5980; Tue, 19 Jan 2010 14:42:43 +0400 (RET) Date: Tue, 19 Jan 2010 10:42:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [commit+doco] Trust PAD types instead of using PAD___XVS. Message-ID: <20100119104243.GT17397@adacore.com> References: <1263808271-10983-1-git-send-email-brobecker@adacore.com> <83ska370s0.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83ska370s0.fsf@gnu.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-01/txt/msg00475.txt.bz2 > > gdb/doc/ChangeLog: > > > > * gdb.texinfo (Ada Glitches): Document new settings > > "set/show ada trust-PAD-over-XVS". > > > > OK to commit the NEWS & doco bits? > > Yes Thanks. Now checked in. > , but I have a question: if this is an obscure setting needed in > some marginal cases, shouldn't it be a "maint" command? I thought about it, and then decided against it: I think that "maint" commands should provide commands that really apply only to the maintainers, commands that allow us to dump data structures, diagnose inconstencies, issues, etc... It's really a judgment call, as we probably have not been completely consistent in the way we name our commands... -- Joel