From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12819 invoked by alias); 22 Nov 2013 01:51:32 -0000 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 Received: (qmail 12622 invoked by uid 89); 22 Nov 2013 01:51:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_50,GARBLED_BODY,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: relay1.mentorg.com Received: from Unknown (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Nov 2013 01:51:31 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1Vjftr-0000Fa-O0 from Yao_Qi@mentor.com ; Thu, 21 Nov 2013 17:51:15 -0800 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 21 Nov 2013 17:51:15 -0800 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.2.247.3; Thu, 21 Nov 2013 17:50:58 -0800 Message-ID: <528EB834.1080205@codesourcery.com> Date: Fri, 22 Nov 2013 02:19:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Tom Tromey CC: Doug Evans , gdb-patches Subject: Re: [PATCH 2/3] set/show code-cache References: <1384996594-20865-1-git-send-email-yao@codesourcery.com> <1384996594-20865-3-git-send-email-yao@codesourcery.com> <528D781A.7070909@codesourcery.com> <871u29h7oa.fsf@fleche.redhat.com> <87k3g1foiq.fsf@fleche.redhat.com> In-Reply-To: <87k3g1foiq.fsf@fleche.redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00666.txt.bz2 On 11/22/2013 05:11 AM, Tom Tromey wrote: > I generally try not to require people to fix existing problems. > My view is that patch submitters aren't responsible for the context; and > that if it matters that much to me, I can fix it myself. (On occasion I > may ask nicely though...) > I'd like to fix existing problems related to my submissions. Patch below updates "ON" and "OFF" in doc in lower case. > But, I think it's ok to require that new bad cases not go in, as a > general rule. Agreed. -- Yao (齐尧) gdb/doc: 2013-11-22 Yao Qi * gdb.texinfo (Caching Target Data): Replace "ON" with "on". (Maintenance Commands): Replace "ON" and "OFF" with "on" and "off" respectively. --- gdb/doc/gdb.texinfo | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 3371835..0359570 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -10861,8 +10861,8 @@ Show the current state of the obsolete remotecache flag. @kindex set stack-cache @item set stack-cache on @itemx set stack-cache off -Enable or disable caching of stack accesses. When @code{ON}, use -caching. By default, this option is @code{ON}. +Enable or disable caching of stack accesses. When @code{on}, use +caching. By default, this option is @code{on}. @kindex show stack-cache @item show stack-cache @@ -37545,7 +37545,7 @@ compiled with the @samp{-pg} compiler option. @item maint set show-debug-regs @itemx maint show show-debug-regs Control whether to show variables that mirror the hardware debug -registers. Use @code{ON} to enable, @code{OFF} to disable. If +registers. Use @code{on} to enable, @code{off} to disable. If enabled, the debug registers values are shown when @value{GDBN} inserts or removes a hardware breakpoint or watchpoint, and when the inferior triggers a hardware-assisted breakpoint or watchpoint. -- 1.7.7.6