This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC 3.3, GCC 3.4

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: tromey at redhat dot com, dje at watson dot ibm dot com, jbuck at synopsys dot com,gcc at gcc dot gnu dot org
Date: Mon, 3 Feb 2003 15:45:50 -0600
Subject: Re: GCC 3.3, GCC 3.4
References: <20030203150151.132ac454.bkoz@redhat.com><63230000.1044306396@warlock.codesourcery.com>

>Right now, we have a window in which to merge branches.  If you're
>ready, you merge; if you're not, you don't.  We successfuly merged
>some major technology that way for 3.4.

I guess your definition of "ready to merge" is what I don't understand.
Could you please elaborate on it?

If you could, please use as specific examples the pch branch and the new
parser branch. You might also add as an example a branch that is not
ready to merge, just so I have something to compare against.

I'm just thinking about a refinement on the current process, not a
complete overhaul. 

-benjamin

Follow-Ups:
- Re: GCC 3.3, GCC 3.4
  - From: Mark Mitchell

References:
- Re: GCC 3.3, GCC 3.4
  - From: Benjamin Kosnik
- Re: GCC 3.3, GCC 3.4
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]