From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: gcc-patches@gcc.gnu.org, <gcc@gcc.gnu.org>,
Alexandre Oliva <aoliva@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>
Subject: Current GCC status (was: PATCH: Fix in-source configuration regression from gcc 3.0.4)
Date: Fri, 26 Apr 2002 04:20:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <oradrt6uzy.fsf@free.redhat.lsd.ic.unicamp.br>
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 />
next parent reply other threads:[~2002-04-26 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <oradrt6uzy.fsf@free.redhat.lsd.ic.unicamp.br>
2002-04-26 4:20 ` Gerald Pfeifer [this message]
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
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=Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).