From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7030 invoked by alias); 1 Aug 2012 14:48:18 -0000 Received: (qmail 7020 invoked by uid 22791); 1 Aug 2012 14:48:17 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 01 Aug 2012 14:48:03 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0M8200B00ZP4DK00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Wed, 01 Aug 2012 17:47:20 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M8200ATHZQVOJD0@a-mtaout20.012.net.il>; Wed, 01 Aug 2012 17:47:20 +0300 (IDT) Date: Wed, 01 Aug 2012 14:48:00 -0000 From: Eli Zaretskii Subject: Re: [RFA 5/5] Explicit linespecs - documentation In-reply-to: <50190306.7080500@redhat.com> To: Pedro Alves Cc: keiths@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838vdyekk1.fsf@gnu.org> References: <50120FE7.8060100@redhat.com> <83394djvm1.fsf@gnu.org> <50190306.7080500@redhat.com> X-IsSubscribed: yes 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: 2012-08/txt/msg00025.txt.bz2 > Date: Wed, 01 Aug 2012 11:20:54 +0100 > From: Pedro Alves > CC: Keith Seitz , gdb-patches@sourceware.org > > On 07/27/2012 12:23 PM, Eli Zaretskii wrote: > > This is too implementation oriented, and thus not really appropriate > > for the user manual. The text should: > > > > . explain what is an explicit spec, in a way that clarifies why it > > is called "explicit" (so that users could make a mental note of > > that, which will facilitate remembering the terminology); > > Or maybe (shocking suggestion follows), not even calling > "explicit linespecs" "linespecs" at all. IOW, you either use linespecs, > or explicit locations. Not shocking at all, at least not for me. I could go with "explicit locations". We still need to say at least something to explain what's the "explicit" part doing there.