From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'André Pönitz'" <andre.poenitz@mathematik.tu-chemnitz.de>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: 'Stan Shebs' <stanshebs@earthlink.net>,
"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: RE: RFC: gdb web page patch for git conversion
Date: Fri, 06 Sep 2013 19:50:00 -0000 [thread overview]
Message-ID: <E59706EF8DB1D147B15BECA3322E4BDC1C47FFEC@eusaamb103.ericsson.se> (raw)
In-Reply-To: <20130904193356.GB5348@klara.mpi.htwm.de>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of André Pönitz
> Sent: Wednesday, September 04, 2013 3:34 PM
> To: Joel Brobecker
> Cc: Stan Shebs; gdb-patches@sourceware.org
> Subject: Re: RFC: gdb web page patch for git conversion
>
> On Wed, Sep 04, 2013 at 06:09:43AM -0700, Joel Brobecker wrote:
> > > My semi-baked plan for the web site redesign, as seen at
> > >
> > > http://sourceware.org/gdb/wiki/WebsiteRedesign
> > >
> > > includes a git migration.
> >
> > Interesting plan!
> >
> > One of my complaints about the current website is that it's really
> > obscure which version of the GDB documentation is available where,
> > and whether we (the developers) would prefer you to look at the
> > documentation from a release, or from the HEAD.
>
> As a somewhat related, general remark: It would be nice if
> GDB documentation
> tagged new features with the version in which they are first
> implemented.
>
> From a frontend developer's point of view the decision which
> feature should
> to be supported is often driven by what version of GDB common
> distributions
> ship. Having a feature tagged as "new and officially
> supported in version
> x.y.z" is a more robust approach than trying to deduce
> "official" blessing
> from change logs, patches, and NEWS entries.
I second the motion :)
Marc
next prev parent reply other threads:[~2013-09-06 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 20:15 Tom Tromey
2013-08-29 20:56 ` Joel Brobecker
2013-09-02 18:18 ` Pedro Alves
2013-09-03 13:18 ` Joel Brobecker
2013-09-03 14:44 ` Pedro Alves
2013-09-03 19:07 ` Stan Shebs
2013-09-04 13:09 ` Joel Brobecker
2013-09-04 19:34 ` André Pönitz
2013-09-06 19:50 ` Marc Khouzam [this message]
2013-09-03 19:19 ` Thomas Schwinge
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=E59706EF8DB1D147B15BECA3322E4BDC1C47FFEC@eusaamb103.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=andre.poenitz@mathematik.tu-chemnitz.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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