From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: Thoughts on the GDB "documentation" web page
Date: Mon, 09 Nov 2009 20:09:00 -0000 [thread overview]
Message-ID: <200911091848.46732.pedro@codesourcery.com> (raw)
In-Reply-To: <20091109174427.GR22192@adacore.com>
On Monday 09 November 2009 17:44:27, Joel Brobecker wrote:
> | 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:
> | [...]
>
I never quite understood the policy of having "last release" up only.
Why not have something like the gcc folks have?
http://gcc.gnu.org/onlinedocs/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
These are manuals for the latest releases.
* GDB 7.0 manuals:
o <URL>GDB User Manual</URL> (<URL>also in PDF</URL> or <URL>PostScript</URL> or an <URL>HTML tarball</URL>)
o <URL>GDB Internals Manual</URL> (<URL>also in PDF</URL> or <URL>PostScript</URL> or an <URL>HTML tarball</URL>)
* GDB 6.8 manuals:
o GDB User Manual (also in PDF or PostScript or an HTML tarball)
o GDB Internals Manual (also in PDF or PostScript or an HTML tarball)
* GDB 6.7 manuals:
o GDB User Manual (also in PDF or PostScript or an HTML tarball)
o GDB Internals Manual (also in PDF or PostScript or an HTML tarball)
...
Current development
Please note that the following documentation refers to current development. Some information may not be applicable to any existing release.
o GDB User Manual (also in PDF or PostScript or an HTML tarball)
o GDB Internals Manual (also in PDF or PostScript or an HTML tarball)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This gives emphasis to _releases_, which, IMO is the right
thing to do.
One problem with the "last release" kind of links is
that "last release" is not stable over time. A scheme like
the above has no such problem. A cross-link from a random
site to to a page in our 6.8 manual should be live forever;
something that is not true currently.
--
Pedro Alves
next prev parent reply other threads:[~2009-11-09 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 18:48 Joel Brobecker
2009-11-09 19:39 ` Eli Zaretskii
2009-11-09 20:09 ` Pedro Alves [this message]
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=200911091848.46732.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=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