From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 90703 invoked by alias); 6 May 2015 15:36:16 -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 90692 invoked by uid 89); 6 May 2015 15:36:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout28.012.net.il Received: from mtaout28.012.net.il (HELO mtaout28.012.net.il) (80.179.55.184) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 06 May 2015 15:36:10 +0000 Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NNX00M00PH02G00@mtaout28.012.net.il> for gdb-patches@sourceware.org; Wed, 06 May 2015 18:35:07 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NNX00LLPPYIQK20@mtaout28.012.net.il>; Wed, 06 May 2015 18:35:06 +0300 (IDT) Date: Wed, 06 May 2015 15:36:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 3/3] Documentation changes for the new zhexadecimal format In-reply-to: <554A1D90.10707@codesourcery.com> To: Luis Machado Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83sib9ra4w.fsf@gnu.org> References: <1430490758-23247-1-git-send-email-lgustavo@codesourcery.com> <1430490758-23247-4-git-send-email-lgustavo@codesourcery.com> <83vbgcqqu9.fsf@gnu.org> <554A1D90.10707@codesourcery.com> X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00108.txt.bz2 > Date: Wed, 6 May 2015 10:56:32 -0300 > From: Luis Machado > CC: > > On 05/01/2015 12:07 PM, Eli Zaretskii wrote: > >> From: Luis Machado > >> Date: Fri, 1 May 2015 11:32:38 -0300 > >> > >> This patch updates the documentation to reflect the addition of the new > >> zhexadecimal format option for -var-set-format and also adds a NEWS entry > >> for the change. > > > > OK, but should we perhaps explain what zhexadecimal means? I didn't > > know about it until I read this patch. > > I'm not too sure where that explanation should go. It should be near the first use of this term. > What about 'zero-padded-hexadecimal'? Too long? Yes, and I don't think we should go to such extremes. Just explaining the term the first time it is used in the manual should be OK.