From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] main.c (captured_main): Alphabetically sort long_options.
Date: Mon, 06 Dec 2010 20:33:00 -0000 [thread overview]
Message-ID: <AANLkTi=w_bU+r4V3QZxA_PkccX9CcP+hgVseT7ZSiLDj@mail.gmail.com> (raw)
In-Reply-To: <m3sjyaabyt.fsf@fleche.redhat.com>
On Mon, Dec 6, 2010 at 12:22 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> fyi, I will check this in in two days if there are no objections.
>
> It is fine by me.
>
> Doug> A good next step would be update --help output,
> Doug> but I was going to wait until after this goes in.
>
> FWIW I think --help output is most useful when it is broken into
> sections, and then sorting is applied in each section. See "tar" or
> "automake" for reasonable examples.
Yeah, good point.
If you compare --help output with the contents of long_options, you'll
see --help is in need of some TLC.
prev parent reply other threads:[~2010-12-06 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 19:41 Doug Evans
2010-12-06 20:22 ` Tom Tromey
2010-12-06 20:33 ` Doug Evans [this message]
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='AANLkTi=w_bU+r4V3QZxA_PkccX9CcP+hgVseT7ZSiLDj@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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