From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: updates on the GDB online documentation
Date: Mon, 09 Nov 2009 20:53:00 -0000 [thread overview]
Message-ID: <m3fx8nfoli.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200911091939.30934.pedro@codesourcery.com> (Pedro Alves's message of "Mon, 9 Nov 2009 19:39:30 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> 1 - currently sources documentation is too prominent.
Pedro> People tend to link to current development sources, without
Pedro> realizing it, when they should be linking to a particular
Pedro> release's docs, and those should be stable forever (or as much
Pedro> as possible anyway), but aren't.
FWIW, GCC does this nicely, see:
http://gcc.gnu.org/onlinedocs/
In particular it is nicely separated by version, with the development
docs at the end, where you're unlikely to click on them by mistake.
Tom
next prev parent reply other threads:[~2009-11-09 20:09 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
2009-11-09 20:53 ` Tom Tromey [this message]
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=m3fx8nfoli.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
/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