From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82135 invoked by alias); 14 Jan 2016 16:42:03 -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 82103 invoked by uid 89); 14 Jan 2016 16:42:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=phone X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 14 Jan 2016 16:42:01 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id CC4618EA49; Thu, 14 Jan 2016 16:42:00 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u0EGfxWF001975; Thu, 14 Jan 2016 11:42:00 -0500 Message-ID: <5697CFD7.70808@redhat.com> Date: Thu, 14 Jan 2016 16:42:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Eli Zaretskii CC: gdb-patches@sourceware.org Subject: Re: [PATCH 2/2] Star wildcard ranges (e.g., "info thread 2.*") References: <1452702886-17749-1-git-send-email-palves@redhat.com> <1452702886-17749-3-git-send-email-palves@redhat.com> <83k2ndifd4.fsf@gnu.org> <569782EB.2030509@redhat.com> <8337u0i1ac.fsf@gnu.org> In-Reply-To: <8337u0i1ac.fsf@gnu.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-01/txt/msg00308.txt.bz2 On 01/14/2016 04:16 PM, Eli Zaretskii wrote: >> Date: Thu, 14 Jan 2016 11:13:47 +0000 >> From: Pedro Alves >> CC: gdb-patches@sourceware.org >> >>>> +* In commands that accept thread IDs lists, you can now refer to all >>> >>> "thread ID lists", only one word in plural. Or maybe even better: >>> "lists of thread IDs". >> >> Hmm, going further, I think that "list" should be singular too: >> >> In commands that accept a thread ID list, you can now refer to all >> In commands that accept a list of thread IDs, you can now refer to all >> >> I prefer the former because "thread ID list" is a defined term in >> the manual. > > I won't bykeshed over it, but just so you know: use of double "status > constructus" in English is not a good style, because it is ambiguous > -- is "thread ID list" an ID list of a thread or a list of thread > IDs? The simple "list of thread IDs" disambiguates that. I really don't won't to bikeshed over it either, so I'll change it, though, I'd say that it's only ambiguous when read out of context, and I'd argue that for the former you'd want to write "thread's ID list". I guess I just see it as being the same as saying "the phone number list". > Thanks, this is OK. Thanks, Pedro Alves