public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC
@ 2010-06-28 13:50 Richard Guenther
  2010-06-28 14:00 ` Arnaud Charlet
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Richard Guenther @ 2010-06-28 13:50 UTC (permalink / raw)
  To: gcc, gcc-patches, fortran, libstdc++


The trunk is frozen for all changes starting this Wednesday, 20:00 UTC
in preparation for merging the mem-ref2 branch.  The freeze is expected
to last until early Friday morning.  An explicit un-freeze mail will
be sent as a reply to this mail.

Thanks.
Richard.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC
  2010-06-28 13:50 Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC Richard Guenther
@ 2010-06-28 14:00 ` Arnaud Charlet
  2010-06-28 14:10   ` Trunk frozen for mem-ref2 merge starting Wed, Jun 30th " Richard Guenther
  2010-06-28 16:58 ` Trunk frozen for mem-ref2 merge starting Wed, Jun 28th " Jack Howarth
  2010-07-02  8:38 ` Richard Guenther
  2 siblings, 1 reply; 6+ messages in thread
From: Arnaud Charlet @ 2010-06-28 14:00 UTC (permalink / raw)
  To: Richard Guenther; +Cc: gcc, gcc-patches, fortran, libstdc++

> The trunk is frozen for all changes starting this Wednesday, 20:00 UTC

Web will be the 30th, not the 28th, can you confirm the date?

Arno

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Trunk frozen for mem-ref2 merge starting Wed, Jun 30th 20:00 UTC
  2010-06-28 14:00 ` Arnaud Charlet
@ 2010-06-28 14:10   ` Richard Guenther
  0 siblings, 0 replies; 6+ messages in thread
From: Richard Guenther @ 2010-06-28 14:10 UTC (permalink / raw)
  To: Arnaud Charlet; +Cc: gcc, gcc-patches, fortran, libstdc++

On Mon, 28 Jun 2010, Arnaud Charlet wrote:

> > The trunk is frozen for all changes starting this Wednesday, 20:00 UTC
> 
> Web will be the 30th, not the 28th, can you confirm the date?

Whoops sorry - 30th indeed.  This is what you get for picking the
date off your clock instead of looking at a calendar.

So,

  Trunk frozen for mem-ref2 merge starting Wed, Jun 30th 20:00

Thanks for noticing,
Richard.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC
  2010-06-28 13:50 Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC Richard Guenther
  2010-06-28 14:00 ` Arnaud Charlet
@ 2010-06-28 16:58 ` Jack Howarth
  2010-06-29  9:59   ` Richard Guenther
  2010-07-02  8:38 ` Richard Guenther
  2 siblings, 1 reply; 6+ messages in thread
From: Jack Howarth @ 2010-06-28 16:58 UTC (permalink / raw)
  To: Richard Guenther; +Cc: gcc, gcc-patches, fortran, libstdc++

On Mon, Jun 28, 2010 at 02:59:39PM +0200, Richard Guenther wrote:
> 
> The trunk is frozen for all changes starting this Wednesday, 20:00 UTC
> in preparation for merging the mem-ref2 branch.  The freeze is expected
> to last until early Friday morning.  An explicit un-freeze mail will
> be sent as a reply to this mail.
> 
> Thanks.
> Richard.

Richard,
   Is there a tentative list yet of which other branches are likely
to be merged into gcc 4.6? In particular, I was wondering if lipo
was going to make the cut.
                Jack

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC
  2010-06-28 16:58 ` Trunk frozen for mem-ref2 merge starting Wed, Jun 28th " Jack Howarth
@ 2010-06-29  9:59   ` Richard Guenther
  0 siblings, 0 replies; 6+ messages in thread
From: Richard Guenther @ 2010-06-29  9:59 UTC (permalink / raw)
  To: Jack Howarth; +Cc: gcc, gcc-patches, fortran, libstdc++

On Mon, 28 Jun 2010, Jack Howarth wrote:

> On Mon, Jun 28, 2010 at 02:59:39PM +0200, Richard Guenther wrote:
> > 
> > The trunk is frozen for all changes starting this Wednesday, 20:00 UTC
> > in preparation for merging the mem-ref2 branch.  The freeze is expected
> > to last until early Friday morning.  An explicit un-freeze mail will
> > be sent as a reply to this mail.
> > 
> > Thanks.
> > Richard.
> 
> Richard,
>    Is there a tentative list yet of which other branches are likely
> to be merged into gcc 4.6? In particular, I was wondering if lipo
> was going to make the cut.

The RMs have not been made aware of any other planned merges.

Richard.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC
  2010-06-28 13:50 Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC Richard Guenther
  2010-06-28 14:00 ` Arnaud Charlet
  2010-06-28 16:58 ` Trunk frozen for mem-ref2 merge starting Wed, Jun 28th " Jack Howarth
@ 2010-07-02  8:38 ` Richard Guenther
  2 siblings, 0 replies; 6+ messages in thread
From: Richard Guenther @ 2010-07-02  8:38 UTC (permalink / raw)
  To: gcc, gcc-patches, fortran, libstdc++

On Mon, 28 Jun 2010, Richard Guenther wrote:

> The trunk is frozen for all changes starting this Wednesday, 20:00 UTC
> in preparation for merging the mem-ref2 branch.  The freeze is expected
> to last until early Friday morning.  An explicit un-freeze mail will
> be sent as a reply to this mail.

The trunk is now open again for development.

Thanks,
Richard.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-07-02  8:38 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-06-28 13:50 Trunk frozen for mem-ref2 merge starting Wed, Jun 28th 20:00 UTC Richard Guenther
2010-06-28 14:00 ` Arnaud Charlet
2010-06-28 14:10   ` Trunk frozen for mem-ref2 merge starting Wed, Jun 30th " Richard Guenther
2010-06-28 16:58 ` Trunk frozen for mem-ref2 merge starting Wed, Jun 28th " Jack Howarth
2010-06-29  9:59   ` Richard Guenther
2010-07-02  8:38 ` Richard Guenther

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).