* Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4) [not found] <oradrt6uzy.fsf@free.redhat.lsd.ic.unicamp.br> @ 2002-04-26 4:20 ` Gerald Pfeifer 2002-04-26 8:56 ` Alexandre Oliva 2002-04-26 10:48 ` Mark Mitchell [not found] ` <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at> 1 sibling, 2 replies; 5+ messages in thread From: Gerald Pfeifer @ 2002-04-26 4:20 UTC (permalink / raw) To: gcc-patches, gcc, Alexandre Oliva; +Cc: Mark Mitchell On 24 Apr 2002, Alexandre Oliva wrote: > I'm not sure this has ever been approved, sorry. Please check it in > mainline. I'd approve it for the 3.1 branch too, if I knew of its > current status, but I've still have a lot of catching up left in the > GCC mailing list too :-( This is an issue that has been coming up quite often, recently, and even in the context of regular contributors like you, so apparently there is a communications problem. Which I, as the one responsible for the web pages, should address. ;-) Add a new section on the status of our release branches and mainline. (Mark, perhaps you could double check this?) Gerald Index: index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v retrieving revision 1.300 diff -u -3 -p -r1.300 index.html --- index.html 19 Apr 2002 07:52:28 -0000 1.300 +++ index.html 26 Apr 2002 11:17:57 -0000 @@ -136,11 +136,32 @@ GNU/Linux) and cross targets and use an <a href="benchmarks/">various benchmark suites and automated testers</a> to maintain and improve quality.</p> -<p><a href="gcc-3.0/">GCC 3.0.4</a> is the current release, and we are -working on the next major release, GCC 3.1 -(<a href="gcc-3.1/criteria.html">release criteria</a>, -<a href="gcc-3.1/changes.html">changes</a>). -</p> + +<dl> +<dt><strong>Current release series:</strong> + <a href="gcc-3.0/">GCC 3.0</a> +</dt> +<dd> + Latest release: GCC 3.0.4 + <br /> + Open for all maintainers. +</dd> +<dt><strong>Active release branch:</strong> + GCC 3.1 (<a href="gcc-3.1/criteria.html">release criteria</a>, + <a href="gcc-3.1/changes.html">changes</a>) +</dt> +<dd> + No release yet. + <br /> + Non-documentation commits require approval by release manager. +</dd> +<dt><strong>Active development (mainline):</strong> + will become GCC 3.2 +</dt> +<dd> + Open for all maintainers. +</dd> +</dl> <hr /> ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4) 2002-04-26 4:20 ` Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4) Gerald Pfeifer @ 2002-04-26 8:56 ` Alexandre Oliva 2002-04-26 10:48 ` Mark Mitchell 1 sibling, 0 replies; 5+ messages in thread From: Alexandre Oliva @ 2002-04-26 8:56 UTC (permalink / raw) To: Gerald Pfeifer; +Cc: gcc-patches, gcc, Mark Mitchell On Apr 26, 2002, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote: > This is an issue that has been coming up quite often, recently, and > even in the context of regular contributors like you, so apparently > there is a communications problem. I supposed the problem was on my end, just because I was 2-3 weeks behind in the GCC mailing lists. It didn't occur to me to look for the information in the web site, anyway :-( Thanks, -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{cygnus.com, redhat.com} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4) 2002-04-26 4:20 ` Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4) Gerald Pfeifer 2002-04-26 8:56 ` Alexandre Oliva @ 2002-04-26 10:48 ` Mark Mitchell 1 sibling, 0 replies; 5+ messages in thread From: Mark Mitchell @ 2002-04-26 10:48 UTC (permalink / raw) To: Gerald Pfeifer, gcc-patches, gcc, Alexandre Oliva --On Friday, April 26, 2002 01:20:38 PM +0200 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote: > On 24 Apr 2002, Alexandre Oliva wrote: >> I'm not sure this has ever been approved, sorry. Please check it in >> mainline. I'd approve it for the 3.1 branch too, if I knew of its >> current status, but I've still have a lot of catching up left in the >> GCC mailing list too :-( > > This is an issue that has been coming up quite often, recently, and > even in the context of regular contributors like you, so apparently > there is a communications problem. > > Which I, as the one responsible for the web pages, should address. ;-) > > Add a new section on the status of our release branches and mainline. > > (Mark, perhaps you could double check this?) Looks right to me. Thanks! -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at>]
* Re: Current GCC status (was: PATCH: Fix in-source configuration regressionfrom gcc 3.0.4) [not found] ` <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at> @ 2002-04-26 13:04 ` Jonathan Lennox 2002-04-26 14:06 ` Gerald Pfeifer 0 siblings, 1 reply; 5+ messages in thread From: Jonathan Lennox @ 2002-04-26 13:04 UTC (permalink / raw) To: gcc-patches, gcc Gerald Pfeifer writes: > Add a new section on the status of our release branches and mainline. Should there be an item added to the release checklist to update this page when you make a release? -- Jonathan Lennox lennox@cs.columbia.edu ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Current GCC status (was: PATCH: Fix in-source configuration regressionfrom gcc 3.0.4) 2002-04-26 13:04 ` Current GCC status (was: PATCH: Fix in-source configuration regressionfrom " Jonathan Lennox @ 2002-04-26 14:06 ` Gerald Pfeifer 0 siblings, 0 replies; 5+ messages in thread From: Gerald Pfeifer @ 2002-04-26 14:06 UTC (permalink / raw) To: Jonathan Lennox; +Cc: gcc-patches, gcc On Fri, 26 Apr 2002, Jonathan Lennox wrote: >> Add a new section on the status of our release branches and mainline. > Should there be an item added to the release checklist to update this page > when you make a release? It's already there: item #5. (Though patches with improvements (also in wording) are always welcome. ;-) ) Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-04-26 20:40 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <oradrt6uzy.fsf@free.redhat.lsd.ic.unicamp.br> 2002-04-26 4:20 ` Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4) Gerald Pfeifer 2002-04-26 8:56 ` Alexandre Oliva 2002-04-26 10:48 ` Mark Mitchell [not found] ` <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at> 2002-04-26 13:04 ` Current GCC status (was: PATCH: Fix in-source configuration regressionfrom " Jonathan Lennox 2002-04-26 14:06 ` Gerald Pfeifer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).