Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] gcore: add --help and --version options
Date: Thu,  6 Mar 2025 17:10:21 +0000	[thread overview]
Message-ID: <cover.1741280898.git.aburgess@redhat.com> (raw)

The new gstack script has --help and --version options, which is more
than the older gcore script has!

This series adds these options to gcore, and also fixes a minor doc
typo relating to gcore.

Thanks,
Andrew

---

Andrew Burgess (3):
  gcore: add -v or --version option to show version number
  gcore: add -h|--help options, and improve help/usage message output
  gcore/doc: fix mistake in the gcore man page

 gdb/Makefile.in              |  7 ++--
 gdb/NEWS                     |  4 +++
 gdb/configure                |  5 ++-
 gdb/configure.ac             |  2 +-
 gdb/doc/gdb.texinfo          | 13 +++++--
 gdb/{gcore.in => gcore-1.in} | 69 ++++++++++++++++++++++++++++++++----
 6 files changed, 83 insertions(+), 17 deletions(-)
 rename gdb/{gcore.in => gcore-1.in} (68%)


base-commit: a6bc00ff35a42d6d555aa8de97d427074151ae47
-- 
2.47.1


             reply	other threads:[~2025-03-06 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 17:10 Andrew Burgess [this message]
2025-03-06 17:10 ` [PATCH 1/3] gcore: add -v or --version option to show version number Andrew Burgess
2025-03-06 17:31   ` Eli Zaretskii
2025-03-06 17:10 ` [PATCH 2/3] gcore: add -h|--help options, and improve help/usage message output Andrew Burgess
2025-03-06 17:33   ` Eli Zaretskii
2025-03-06 17:10 ` [PATCH 3/3] gcore/doc: fix mistake in the gcore man page Andrew Burgess
2025-03-06 17:32   ` Eli Zaretskii
2025-03-06 20:16 ` [PATCH 0/3] gcore: add --help and --version options Tom Tromey
2025-03-06 20:19 ` Tom Tromey

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=cover.1741280898.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@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