Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] gdb: gdb.1 - order options alphabetically in manual 	page
Date: Thu, 10 Sep 2009 01:08:00 -0000	[thread overview]
Message-ID: <20090910010821.GG20694@adacore.com> (raw)
In-Reply-To: <87hbvct24x.fsf@jondo.cante.net>

> Motivation:
> 
>     Order of the options would follow the convention used in other GNU
>     programs lik Cf. cp(1), mv(1), etc.

I am not aware of any conflicting requirement regarding the order
that the GDB command-line switches have to follow in the man pages,
so your suggestion makes sense.

> I have assigned papers to FSF (Emacs). Please let me know if more is
> needed.

Unfortunately, I do not think that we can use your emacs assignment
for GDB code. The problem is that I have no idea if it is OK to accept
changes of this nature. Normally, the guidelines for accepting patches
without an assignment on file is that it should be 10 lines or less.
So your patch does not qualify. But on the other hand, it is the obvious
implementation of the idea of ordering the switches by alphabetical
order.

Does anyone know? Should I enquire?

-- 
Joel


  reply	other threads:[~2009-09-10  1:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 18:20 Jari Aalto
2009-09-10  1:08 ` Joel Brobecker [this message]
2009-09-10  1:32   ` Daniel Jacobowitz
2009-09-10 22:52     ` Joel Brobecker
2009-09-11  8:10       ` Eli Zaretskii
2009-09-11 23:17         ` Joel Brobecker
2009-09-12  8:31           ` Eli Zaretskii
2009-09-12 18:35             ` Joel Brobecker
2009-10-11 21:22               ` Daniel Jacobowitz
2009-10-11 23:25                 ` Joel Brobecker
2009-09-16 15:49 ` Joel Brobecker
2009-09-16 17:23   ` Eli Zaretskii

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=20090910010821.GG20694@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jari.aalto@cante.net \
    /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