From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Thoughts on the GDB "documentation" web page
Date: Mon, 09 Nov 2009 18:48:00 -0000 [thread overview]
Message-ID: <20091109174427.GR22192@adacore.com> (raw)
This is regarding: http://www.sourceware.org/gdb/documentation/
I find the "documentations page" not as straightforward as I'd like it
to be. In particular, the "Online GDB Manuals" sections, which looks
like this:
| Online GDB manuals
| Documentation generated from the <URL: current_cvs>current</URL>
| sources are available online:
|
| <URL: GDB TOC>GDB User Manual<URL> (<URL: PDF>gziped</URL> PDF)
| Describes how to use GDB.
| Translations are also available:
| * Japanese, by Kazuhisa Ichikawa as part of KI's
| Unofficial GNU Manual Translation Project.
| * Russian, by Dmitry Sivachenko.
|
| <URL: GDB Internals TOC>GDB Internals Manual</URL> (gziped PDF)
| Technical details of the internals of GDB.
|
| The documentation is also available for <URL: head-onlinedocs>
| download</URL> in a number of different formats including (HTML,
| DVI, PS and PDF).
|
| Versions of the documentation generated from the last
| <URL:release-onlinedocs>release</URL> and most recent
| <URL:branch-onlinedocs>branch</URL> are also available.
What I find confusing is how to get to the "onlinedocs" page
for the HEAD. It takes careful reading every single time I go
to that page to find the link (clicking on "download"). Similarly,
it takes careful reading to find where the release and branch
documentation is located. It would be nice to make everything
a little more structured.
I would like to reorganize this a little. Here is what the entire
page looks like, right now:
| GDB Documentation
|
| Printed Manuals
| <one-line explaining how to get printed manuals from the GNU Press>
|
| Online GDB Manuals
| <see above>
|
| Reference Materials
| Additional documentation includes:
| [...]
|
| GDB interfaces and standards
| [...]
I am not sure I have been able to come up with anything better, so
suggestions always welcome. Here is what I propose. Revamp the page
as follow:
| GDB Documentation
|
| <URL>GDB User Manual</URL> <URL>GDB Internals Manual</URL>
| (gzipped <URL>PDF</URL>) (gzipped <URL>PDF</URL>)
| Describes how to use GDB. Technical details of the internals
| of GDB.
|
| Online GDB Documentation
| GDB provides a set of documents (including manuals) that are
| available from the links below:
| * For the <URL>last release</URL>
| * For the <URL>head branch</URL>
| * For the currently active <URL>branch</URL>
|
| Printed Manuals
| <contents unchanged>
|
| Translated manuals
| Translations of the GDB manual are also available:
| [...]
Thoughts?
--
Joel
next reply other threads:[~2009-11-09 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 18:48 Joel Brobecker [this message]
2009-11-09 19:39 ` Eli Zaretskii
2009-11-09 20:09 ` Pedro Alves
2009-11-09 22:36 ` Joel Brobecker
2009-11-10 2:12 ` Joel Brobecker
2009-11-10 7:25 ` Pedro Alves
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=20091109174427.GR22192@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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