This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: gdb web page patch for git conversion
- From: André Pönitz <andre dot poenitz at mathematik dot tu-chemnitz dot de>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Stan Shebs <stanshebs at earthlink dot net>, gdb-patches at sourceware dot org
- Date: Wed, 4 Sep 2013 21:33:57 +0200
- Subject: Re: RFC: gdb web page patch for git conversion
- Authentication-results: sourceware.org; auth=none
- References: <87ob8gp82d dot fsf at fleche dot redhat dot com> <20130829205557 dot GA3315 at adacore dot com> <5224D659 dot 2050700 at redhat dot com> <20130903131803 dot GA2809 at adacore dot com> <5225F5D2 dot 3050509 at redhat dot com> <52263373 dot 3080401 at earthlink dot net> <20130904130943 dot GA2855 at adacore dot com>
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.
Andre'