From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] gdbserver: allow the --debug command line option to take a value
Date: Tue, 05 Dec 2023 15:06:13 +0200 [thread overview]
Message-ID: <8334wg6bp6.fsf@gnu.org> (raw)
In-Reply-To: <87cyvlgdhe.fsf@redhat.com> (message from Andrew Burgess on Tue, 05 Dec 2023 10:17:33 +0000)
> From: Andrew Burgess <aburgess@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Tue, 05 Dec 2023 10:17:33 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> The man page is generated from gdb.texinfo using this magic in
> >> gdb/doc/Makefile.in:
> >
> > And we must have two identical passages in the manual to do that? We
> > cannot generate these man pages using a single copy of the text we are
> > talking about?
>
> I 100% agree with you that it would be better if we could somehow
> structure things so that we could remove the duplication. But I don't
> know what the right way to do that would be, and I don't think it's
> going to be a small task.
>
> Hopefully you're not suggesting that I need to do this in order to
> document a new gdbserver command line option?
No, if this is not trivial to fix, we might as well keep living with
it.
> I guess my question would be: Are the doc parts of this patch good
> enough given the known idiosyncrasies of how the manual is structured?
Yes, thanks.
next prev parent reply other threads:[~2023-12-05 13:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:03 [PATCH 0/3] Improve debug output support in gdbserver Andrew Burgess
2023-11-07 18:03 ` [PATCH 1/3] gdbserver: cleanup monitor_show_help Andrew Burgess
2023-11-22 15:21 ` Andrew Burgess
2023-11-07 18:03 ` [PATCH 2/3] gdbserver: allow the --debug command line option to take a value Andrew Burgess
2023-11-07 19:41 ` Eli Zaretskii
2023-11-30 18:31 ` Andrew Burgess
2023-11-30 19:20 ` Eli Zaretskii
2023-12-04 15:57 ` Andrew Burgess
2023-12-04 16:21 ` Eli Zaretskii
2023-12-05 10:17 ` Andrew Burgess
2023-12-05 13:06 ` Eli Zaretskii [this message]
2023-11-07 18:03 ` [PATCH 3/3] gdbserver: allow for general 'monitor set debug COMPONENT VALUE' use Andrew Burgess
2023-11-17 14:43 ` [PATCH 0/3] Improve debug output support in gdbserver Tom Tromey
2023-11-17 14:55 ` Tom Tromey
2023-11-30 18:44 ` [PATCHv2 " Andrew Burgess
2023-11-30 18:44 ` [PATCHv2 1/3] gdb: fix GDB_DEBUG and GDBSERVER_DEBUG Makefile variables Andrew Burgess
2023-11-30 18:44 ` [PATCHv2 2/3] gdbserver: allow the --debug command line option to take a value Andrew Burgess
2023-11-30 18:44 ` [PATCHv2 3/3] gdbserver: allow for general 'monitor set debug COMPONENT VALUE' use Andrew Burgess
2023-11-30 19:30 ` Eli Zaretskii
2023-12-01 18:02 ` [PATCHv2 0/3] Improve debug output support in gdbserver Tom Tromey
2023-12-08 18:03 ` Andrew Burgess
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=8334wg6bp6.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).