From: Tom de Vries <tdevries@suse.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: gdb and sphinx documentation
Date: Sun, 18 Sep 2022 10:31:43 +0200 [thread overview]
Message-ID: <c37bd31e-1c40-8c2e-cc35-5e9f31930bc4@suse.de> (raw)
Hi,
at the GNU Cauldron, Martin Liška presented a BOF about migrating GCC
documentation to sphinx format (
https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_sphinx_documentation_bof
).
I asked him about the gdb documentation, and he ran the migration
scripts he used for gcc on it. The result is obviously a bit rough, but
gives a nice idea what it could look like.
Please take a look if you're interested ( https://splichal.eu/tmp/gdb ).
Thanks,
- Tom
next reply other threads:[~2022-09-18 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 8:31 Tom de Vries [this message]
2022-09-18 13:06 ` Gaius Mulley
2022-09-18 13:20 ` Eli Zaretskii
2022-09-18 22:25 ` Simon Marchi
2022-09-26 0:03 ` Joel Brobecker
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=c37bd31e-1c40-8c2e-cc35-5e9f31930bc4@suse.de \
--to=tdevries@suse.de \
--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).