From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: 'info os' additions again
Date: Thu, 10 May 2012 18:42:00 -0000 [thread overview]
Message-ID: <4FAC0C15.8070009@earthlink.net> (raw)
In-Reply-To: <4FAC065C.4030901@redhat.com>
On 5/10/12 11:18 AM, Pedro Alves wrote:
> On 05/10/2012 07:12 PM, Stan Shebs wrote:
>
>> They're waiting for the GDB bits (including the MI patch which is in my queue) to become available, which is why I want to get this resolved one way or another. It's a little ironic that Eclipse folks, who don't care about command-line syntax, are being blocked on a discussion of command-line syntax. :-)
>>
>> If everybody is tired of the issue, I'll just make a decision; things can always be changed later.
>
> What kind of decision? What would exactly be the alternative?
>
To pick one of "info os" and "info linux". I don't think there are many
other credible alternatives; the subcommand should be a single short
word, with the rest of the work to be done by subsubcommands and/or
arguments. "info unix" or "info posix" would qualify, but historically
we've tended to avoid using those terms in GDB commands, and one could
argue that they have the same vagueness/overloading issue that "os" does.
Stan
next prev parent reply other threads:[~2012-05-10 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 22:49 Stan Shebs
2012-05-08 23:55 ` Joel Brobecker
2012-05-09 4:46 ` Eli Zaretskii
2012-05-09 21:17 ` Stan Shebs
2012-05-10 5:21 ` Eli Zaretskii
2012-05-10 12:22 ` Pedro Alves
2012-05-10 18:13 ` Stan Shebs
2012-05-10 18:18 ` Pedro Alves
2012-05-10 18:42 ` Stan Shebs [this message]
2012-05-10 18:59 ` Pedro Alves
2012-05-10 21:07 ` Stan Shebs
2012-05-11 18:30 ` Pedro Alves
2012-05-12 1:33 ` Matt Rice
2012-05-14 14:52 ` Joel Brobecker
2012-05-11 20:25 ` Marc Khouzam
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=4FAC0C15.8070009@earthlink.net \
--to=stanshebs@earthlink.net \
--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