Re: [wwwdocs] releases.html v/s develop.html

2006-06-02 Thread Ranjit Mathew
On 6/2/06, Gerald Pfeifer <[EMAIL PROTECTED]> wrote: Mind to send/commit a patch to complete releases.html with 4.x releases and add a step to releasing.html? (Basically you just need to revert revision 1.26 of that file.) Joe Buck beat me to it and you applied it for him. Thanks to both of y

Re: [wwwdocs] releases.html v/s develop.html

2006-06-02 Thread Gerald Pfeifer
On Thu, 1 Jun 2006, Joe Buck wrote: > Let's just add the info to the table. Here is a proposed patch. > Note that I resorted by date and added an explanation. I think > that the attempt to sort by release number became increasingly > untenable after 3.4, because we now have heavy overlapping. Be

Re: [wwwdocs] releases.html v/s develop.html

2006-06-01 Thread Joe Buck
On Thu, Jun 01, 2006 at 11:43:09PM +0200, Gerald Pfeifer wrote: > In the eyes of at least some, especially the dates for the old > releases in releases.html are of historical interest, so I'd be > quite hesitant to remove these. > > I'm not sure I agree that it is easy to miss the statement on >

Re: [wwwdocs] releases.html v/s develop.html

2006-06-01 Thread Gerald Pfeifer
On Sun, 14 May 2006, Ranjit Mathew wrote: > Dave Yost points out that a cursory look at the main table > in: > > http://gcc.gnu.org/releases.html > > (which is linked-to from the main page) gives the impression > that 3.4.6 has been our last release. It is very easy to > miss the fine-print-l

[wwwdocs] releases.html v/s develop.html

2006-05-13 Thread Ranjit Mathew
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Dave Yost points out that a cursory look at the main table in: http://gcc.gnu.org/releases.html (which is linked-to from the main page) gives the impression that 3.4.6 has been our last release. It is very easy to miss the fine-print-like