From: Jonathan Lennox <lennox@cs.columbia.edu>
To: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Current GCC status (was: PATCH: Fix in-source configuration regressionfrom gcc 3.0.4)
Date: Fri, 26 Apr 2002 13:04:00 -0000 [thread overview]
Message-ID: <15561.45462.851056.373227@grandcentral.cs.columbia.edu> (raw)
In-Reply-To: <Pine.BSF.4.44.0204261312130.71509-100000@naos.dbai.tuwien.ac.at>
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
next prev parent reply other threads:[~2002-04-26 19:59 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 ` Current GCC status (was: PATCH: Fix in-source configuration regression from " 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 ` Jonathan Lennox [this message]
2002-04-26 14:06 ` Current GCC status (was: PATCH: Fix in-source configuration regressionfrom " 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=15561.45462.851056.373227@grandcentral.cs.columbia.edu \
--to=lennox@cs.columbia.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/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).