public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jari dot aalto at cante dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/10620] New: [PATCH] order options alphabetically in manual page + --long options
Date: Wed, 09 Sep 2009 14:08:00 -0000	[thread overview]
Message-ID: <20090909140815.10620.jari.aalto@cante.net> (raw)

This is "stacked patch" that should be applied after:

  [PATCH] order options alphabetically in manual page
  http://sourceware.org/bugzilla/show_bug.cgi?id=10505

   Direct link: 
   http://sourceware.org/bugzilla/attachment.cgi?id=4125&action=view

It answers to request to prefer --long option syntax (two dashes) for long 
option names as described in bug:

  gdb - Manual and info pages should present GNU --long options
  http://sourceware.org/bugzilla/show_bug.cgi?id=10619

-- 
           Summary: [PATCH] order options alphabetically in manual page + --
                    long options
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: jari dot aalto at cante dot net
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=10620

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 14:08 jari dot aalto at cante dot net [this message]
2009-09-09 14:09 ` [Bug build/10620] " jari dot aalto at cante dot net
2009-09-09 17:18 ` tromey at redhat dot com

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=20090909140815.10620.jari.aalto@cante.net \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).