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 find-debuginfo/27641] please add a minimal description / usage for find-debuginfo
Date: Tue, 18 May 2021 17:22:16 +0000	[thread overview]
Message-ID: <bug-27641-13298-AZiD0vSn4o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27641-13298@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
commit 50b1c95bb2ac23b17079eed41996e61e1185698a
Author: Mark Wielaard <mark@klomp.org>
Date:   Fri Apr 30 00:42:23 2021 +0200

    find-debuginfo.sh: Add --help, --version and man page.

    Add a --version and --help option to find-debuginfo.sh and use that to
    generate a manual page.

            * .gitignore: Add find-debuginfo.sh.1
            * Makefile.am (dist_man_MANS): Add find-debuginfo.sh.1
            (find-debuginfo.sh.1): New make rule.
            * scripts/find-debuginfo.sh (help): New function.
            Handle --version and --help.

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

    Signed-off-by: Mark Wielaard <mark@klomp.org>

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

      parent reply	other threads:[~2021-05-18 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  6:35 [Bug find-debuginfo.sh/27641] New: " doko at debian dot org
2021-04-29 22:46 ` [Bug find-debuginfo.sh/27641] " mark at klomp dot org
2021-05-18 17:22 ` mark at klomp dot org [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=bug-27641-13298-AZiD0vSn4o@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).