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: Making your branches smaller for easier merges

From: "Manuel LÃpez-IbÃÃez" <lopezibanez at gmail dot com>
To: "Daniel Berlin" <dberlin at dberlin dot org>
Cc: "Diego Novillo" <dnovillo at redhat dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>, gcc at gcc dot gnu dot org
Date: Wed, 27 Sep 2006 22:38:45 +0100
Subject: Re: Making your branches smaller for easier merges
References: <4aca3dc20609271337o77f07fdalf85679754e7a80d1@mail.gmail.com> <451AE2CF.9020504@redhat.com> <4aca3dc20609271354y31343217t80ceeebbfac1c989@mail.gmail.com>

On 27/09/06, Daniel Berlin <dberlin@dberlin.org> wrote:

On 9/27/06, Diego Novillo <dnovillo@redhat.com> wrote:
> Daniel Berlin wrote on 09/27/06 16:37:
>
> > If you are just writing a new pass, you can probably get away with
> > branching only a few files, and switching those may be a lot better
> > strategy than branching the entire trunk tree branch to modify 6 files
> > in the gcc dir.
> >
> But this means that I'm at the mercy of mainline random breakage, right?
Yes


Why? Perhaps I am entirely wrong but can't you just don't update (svn
up) those directories that are switched until mainline is in an usable
state?

Cheers,

Manuel.

Follow-Ups:
- Re: Making your branches smaller for easier merges
  - From: Diego Novillo
- Re: Making your branches smaller for easier merges
  - From: Paul Brook

References:
- Making your branches smaller for easier merges
  - From: Daniel Berlin
- Re: Making your branches smaller for easier merges
  - From: Diego Novillo
- Re: Making your branches smaller for easier merges
  - From: Daniel Berlin

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