Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: Thoughts on the GDB "documentation" web page
Date: Mon, 09 Nov 2009 22:36:00 -0000	[thread overview]
Message-ID: <20091109205322.GA27476@adacore.com> (raw)
In-Reply-To: <200911091848.46732.pedro@codesourcery.com>

Thanks for the suggestion.

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 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.

I would be OK with an approach like that.

-- 
Joel


  reply	other threads:[~2009-11-09 20:53 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
2009-11-09 22:36   ` Joel Brobecker [this message]
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=20091109205322.GA27476@adacore.com \
    --to=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