public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: GCC <gcc@gcc.gnu.org>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
		Richard Guenther <rguenther@suse.de>,
	Jakub Jelinek <jakub@redhat.com>
Subject: Re: End of GCC 4.6 Stage 1: October 27, 2010
Date: Sun, 05 Sep 2010 04:23:00 -0000	[thread overview]
Message-ID: <AANLkTi=KDNFoqzzJzCoJRCT0YW8ra1=Nv4CZ9hpV46UL@mail.gmail.com> (raw)
In-Reply-To: <4C7D26EA.6020807@codesourcery.com>

We would like x86_64-w64-mingw32 to become a secondary target for 4.6.
 What has to be checked off for that to happen?  I have an
auto-testsuite-thinger running constantly now and posting results to
the ML (it takes several days to do a full dl/build/test, so it's not
daily, but it's continuous).

On Tue, Aug 31, 2010 at 11:59 AM, Mark Mitchell <mark@codesourcery.com> wrote:
> We (GCC RMs) plan to close GCC 4.6 Stage 1 on or or about October 27,
> 2010 (the closing day of the GCC Summit).  Major features should be
> checked in prior to this point.  Please let us know if you have a major
> feature that you think you will not be able to get checked in prior to
> October 27th.
>
> Thank you,
>
> --
> Mark Mitchell
> CodeSourcery
> mark@codesourcery.com
> (650) 331-3385 x713
>

  reply	other threads:[~2010-09-05  4:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 22:55 Mark Mitchell
2010-09-05  4:23 ` NightStrike [this message]
2010-09-05 18:03   ` Mark Mitchell
2010-09-05 18:23     ` NightStrike
2010-09-05 18:29       ` Mark Mitchell
2010-09-05 18:35         ` NightStrike
2010-09-05 18:40           ` Mark Mitchell
2010-09-05 22:10           ` Gerald Pfeifer
2010-09-05 22:18             ` Tobias Burnus
2010-09-06  9:22               ` Richard Guenther
2010-09-06 16:19                 ` NightStrike
2010-09-06 16:21                   ` Richard Guenther
2010-09-06 16:33                     ` Tim Prince
2010-09-06 17:18                     ` NightStrike
2010-09-06 17:24                       ` Andrew Haley
2010-09-06 17:32                         ` NightStrike
2010-09-20 23:23                           ` NightStrike
2010-09-21 10:01                             ` Jonathan Wakely
2010-09-21 15:09                               ` NightStrike
2010-09-21 17:27                                 ` Dave Korn
2010-09-23 22:09                                   ` NightStrike
2010-10-08 15:56                                     ` NightStrike
2010-10-08 16:06                                       ` Jonathan Wakely
2010-10-08 16:10                                         ` Kai Tietz
2010-10-08 16:54                                         ` NightStrike
2010-10-08 18:04                                         ` Jonathan Wakely
2010-10-08 18:11                                           ` NightStrike
2010-10-09  1:40                                             ` Dave Korn
2011-02-24 17:05                                         ` NightStrike
2010-10-08 21:09                                       ` Richard Guenther
2010-10-08 21:14                                         ` NightStrike
2010-10-09  0:42                                           ` Richard Guenther

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='AANLkTi=KDNFoqzzJzCoJRCT0YW8ra1=Nv4CZ9hpV46UL@mail.gmail.com' \
    --to=nightstrike@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=mark@codesourcery.com \
    --cc=rguenther@suse.de \
    /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).