From: Phil Edwards <pedwards@disaster.jaj.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Benjamin Kosnik <bkoz@redhat.com>, gcc@gcc.gnu.org
Subject: Re: gcc-3_1-branch
Date: Mon, 22 Oct 2001 08:54:00 -0000 [thread overview]
Message-ID: <20011022115600.A12679@disaster.jaj.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0110220853140.27598-100000@naos.dbai.tuwien.ac.at>
On Mon, Oct 22, 2001 at 08:54:57AM +0200, Gerald Pfeifer wrote:
> On Fri, 19 Oct 2001, Benjamin Kosnik wrote:
> > Hey, is the gcc 3.1 branch going to happen? Or is this a 2 month period, and
>
> Yes, but only in a bit less than 4 months: We are now in "Stage 2" of
> the development plan described at < http://gcc.gnu.org/develop.html >;
> the branch will be created at the end of "Stage 3".
We really need an HTML table at the end of develop.html, with the versions
along one axis, the stages/effects along the other axis, and the calendar
dates in the cells.
Why have I not added a patch in this email? I started to, and then I
realized that I don't understand the development plan. :-)
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next prev parent reply other threads:[~2001-10-22 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 15:01 gcc-3_1-branch Benjamin Kosnik
2001-10-21 23:55 ` gcc-3_1-branch Gerald Pfeifer
2001-10-22 8:54 ` Phil Edwards [this message]
2001-10-22 9:02 ` gcc-3_1-branch Joseph S. Myers
2001-10-22 11:19 ` gcc-3_1-branch Gerald Pfeifer
2001-10-22 11:36 ` gcc-3_1-branch Benjamin Kosnik
2001-10-22 12:51 ` gcc-3_1-branch Gerald Pfeifer
2001-10-22 13:24 ` gcc-3_1-branch Phil Edwards
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=20011022115600.A12679@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).