From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: updates on the GDB online documentation
Date: Mon, 09 Nov 2009 20:19:00 -0000 [thread overview]
Message-ID: <200911091939.30934.pedro@codesourcery.com> (raw)
In-Reply-To: <20091109173300.GQ22192@adacore.com>
On Monday 09 November 2009 17:33:00, Joel Brobecker wrote:
> Doug Evans remarked that one of the issues with the texi2html is that
> it uses numbers in its URLs, making the URLs unstable over time.
> For instance:
>
> http://www.sourceware.org/gdb/current/onlinedocs/gdb_5.html#SEC21
>
> Switching back to using makeinfo will improve the situation, as
> the HTML files are now named using the node name, or the chapter/name
> section (not sure which):
>
> Automatic-Overlay-Debugging.html
>
> I will try to commit this change tomorrow.
I don't object to this, but I want to note that IMO, this sidesteps
a more fundamental problem that is:
1 - currently sources documentation is too prominent.
People tend to link to current development sources, without
realizing it, when they should be linking to a particular
release's docs, and those should be stable forever (or as much
as possible anyway), but aren't.
2 - As I noted in the other email, an url like:
http://www.sourceware.org/gdb/onlinedocs/6.8/gdb_5.html#SEC21
, would never have this stableness problem, even if we switched
docs of newer releases to makeinfo or whatever tool we find
is better in 2020. That is, an absolute "6.8", not
"previous release" or some other non-absolute term. If we do decide
to keep older manuals up in the webpage (as I hope we do), we can't
also assume that newer makeinfo/texinfo's grok older manuals
correctly. Note we shouldn't need that --- once a manual is
upload, it should not need regenerating again.
--
Pedro Alves
next prev parent reply other threads:[~2009-11-09 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 18:48 Joel Brobecker
2009-11-09 20:19 ` Pedro Alves [this message]
2009-11-09 20:53 ` Tom Tromey
2009-11-09 22:14 ` Marc Khouzam
2009-11-11 1:01 ` 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=200911091939.30934.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