From: Gabriel Dos Reis <gdr@cs.tamu.edu>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.3 status
Date: Wed, 20 Apr 2005 15:21:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0504201011120.25019@sun> (raw)
In-Reply-To: <043501c54591$779e1370$914d2597@bagio>
On Wed, 20 Apr 2005, Giovanni Bajo wrote:
| Hello Gaby,
|
| do you still confirm the release date which was last reported here:
| http://gcc.gnu.org/ml/gcc/2005-01/msg01253.html
|
| that is, will GCC 3.3.6 released on April, 30th? And will it be the last
| release of the GCC 3.3 series?
All those information are right.
More on that later today.
|
| Thanks,
| Giovanni Bajo
|
|
--
Gabriel Dos Reis
gdr@cs.tamu.edu
Texas A&M University -- Computer Science Department
301, Bright Building -- College Station, TX 77843-3112
next prev parent reply other threads:[~2005-04-20 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 10:56 Giovanni Bajo
2005-04-20 15:21 ` Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 23:55 GCC 3.3 Status S. Bosscher
2003-04-28 8:14 ` Mark Mitchell
2003-04-22 23:14 Mark Mitchell
2003-04-23 14:19 ` Jan Hubicka
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.GSO.4.58.0504201011120.25019@sun \
--to=gdr@cs.tamu.edu \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
/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).