Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Star wildcard ranges (e.g., "info thread 2.*")
Date: Thu, 14 Jan 2016 16:42:00 -0000	[thread overview]
Message-ID: <5697CFD7.70808@redhat.com> (raw)
In-Reply-To: <8337u0i1ac.fsf@gnu.org>

On 01/14/2016 04:16 PM, Eli Zaretskii wrote:
>> Date: Thu, 14 Jan 2016 11:13:47 +0000
>> From: Pedro Alves <palves@redhat.com>
>> 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


  reply	other threads:[~2016-01-14 16:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 16:34 [PATCH 0/2] " Pedro Alves
2016-01-13 16:34 ` [PATCH 1/2] Fix "thread apply $conv_var" and misc other related problems Pedro Alves
2016-01-13 16:34 ` [PATCH 2/2] Star wildcard ranges (e.g., "info thread 2.*") Pedro Alves
2016-01-13 17:00   ` Eli Zaretskii
2016-01-14 11:13     ` Pedro Alves
2016-01-14 16:16       ` Eli Zaretskii
2016-01-14 16:42         ` Pedro Alves [this message]
2016-01-14 11:29   ` Pedro Alves
2016-01-13 16:34 ` [PATCH 0/2] " Pedro Alves
2016-01-13 16:42   ` Pedro Alves
2016-01-14 16:52 ` Simon Marchi
2016-01-15 21:50 ` Pedro Alves
2016-01-14 11:39 Pedro Alves
2016-01-14 11:39 ` [PATCH 2/2] " Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5697CFD7.70808@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox