From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gcore/doc: fix mistake in the gcore man page
Date: Thu, 06 Mar 2025 19:32:16 +0200 [thread overview]
Message-ID: <864j06m5en.fsf@gnu.org> (raw)
In-Reply-To: <1f75c841fe44eb4bbf8c9630ff4e4b128a462c7f.1741280898.git.aburgess@redhat.com> (message from Andrew Burgess on Thu, 6 Mar 2025 17:10:24 +0000)
> From: Andrew Burgess <aburgess@redhat.com>
> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Thu, 6 Mar 2025 17:10:24 +0000
>
> The gcore man page says that the default prefix for a generated core
> file will be 'gcore', i.e. we'll create files like 'gcore.pid'. In
> reality the default is 'core'.
>
> As far as I can tell, the default has been 'core' for years, and the
> docs used to say that the default was 'core', but the docs were
> changed by mistake in commit:
>
> commit 129eb0f1f16dc7a49799a024a7bcb109d954a1e7
> Date: Fri Jul 27 00:52:23 2018 -0400
>
> Improve gcore manpage and clarify "-o" option
>
> So, lets bring the docs back inline with the code.
> ---
> gdb/doc/gdb.texinfo | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This is okay, thanks.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2025-03-06 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 17:10 [PATCH 0/3] gcore: add --help and --version options Andrew Burgess
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 [this message]
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=864j06m5en.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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