From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Pedro Alves'" <pedro@codesourcery.com>,
"'gdb@sourceware.org'" <gdb@sourceware.org>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>
Subject: RE: updates on the GDB online documentation
Date: Mon, 09 Nov 2009 22:14:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5158E460C1@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <200911091939.30934.pedro@codesourcery.com>
> 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.
I agree.
It took me a while to realize that my bookmark titled
"GDB documentation", was pointing to a 'live' document and not the latest GDB.
(I had created the bookmark when I was first starting to use GDB).
Marc
next prev parent reply other threads:[~2009-11-09 20:22 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
2009-11-09 22:14 ` Marc Khouzam [this message]
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=F7CE05678329534C957159168FA70DEC5158E460C1@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.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