From: Mark Mitchell <mark@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: GCC 4.1 Status Report (2005-07-22)
Date: Mon, 25 Jul 2005 22:25:00 -0000 [thread overview]
Message-ID: <42E566DB.7050006@codesourcery.com> (raw)
In-Reply-To: <Pine.BSF.4.62.0507251312050.21428@pulcherrima.dbai.tuwien.ac.at>
Gerald Pfeifer wrote:
> On Fri, 22 Jul 2005, Mark Mitchell wrote:
>
>>We have been in Stage 3 for a little while now. I'm sure a few more
>>patches that were proposed in Stage 2 will find their way into 4.1,
>>but we're approximately feature-complete at this point.
>
>
> I just committed the following update for our main page. If you'd like
> to change "open for bug fixes" to something more strict, please let me
> know.
No, I think that's perfect. Thanks!
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
prev parent reply other threads:[~2005-07-25 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 20:22 Mark Mitchell
2005-07-22 21:02 ` Andrew Pinski
2005-07-22 21:05 ` Mark Mitchell
2005-07-22 21:07 ` Andrew Pinski
2005-07-22 21:08 ` Mark Mitchell
2005-07-22 21:19 ` Andrew Pinski
2005-07-22 21:23 ` Mark Mitchell
2005-07-25 11:15 ` Gerald Pfeifer
2005-07-25 22:25 ` Mark Mitchell [this message]
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=42E566DB.7050006@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.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).