public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/28737] The -u option is not recognised
Date: Mon, 03 Jan 2022 22:27:15 +0000	[thread overview]
Message-ID: <bug-28737-13298-579UjBYjVb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28737-13298@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28737

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Thanks. How odd nobody found this earlier. I had assumed that make distcheck
would have checked this. But that only checks --version and --help. With this
-u and --usage work as expected.

Pushed to main as:

commit 47041a41811fdd401cb868bcb5f9dac6635837ef
Author: Allan McRae <allan@archlinux.org>
Date:   Sun Jan 2 15:23:34 2022 +1000

    Fix -u option

    The -u option was missing from optionsChars resulting in it being
    unrecognised.

    $ debugedit -u
    debugedit: invalid option -- 'u'

    Signed-off-by: Allan McRae <allan@archlinux.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-01-03 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02  5:33 [Bug debugedit/28737] New: " allan at archlinux dot org
2022-01-03 22:27 ` mark at klomp dot org [this message]
2022-01-03 22:30 ` [Bug debugedit/28737] " mark at klomp dot org

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=bug-28737-13298-579UjBYjVb@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=debugedit@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).