Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of lesmikesell@gmail.com
 designates 209.85.216.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <EA9A16E4E64F694BAD262610B0A2515C236B09DD@USALWEXMBX2.infor.com>
References: 
 <CAJnVsRx1vxiJB4d9aJ7Pftn1te4L4wfhLigtsJf7+=T7KvF5_Q@mail.gmail.com>
	<1B05D8F50421E24799AE93B03CC284BE01CD38BE04@CRPMBX01.corp.cbeyond.net>
	<CAJnVsRyuaOPdaX98p=S-aN3jUFE932Xcdo01-nytzKcqVzDCrA@mail.gmail.com>
	<EA9A16E4E64F694BAD262610B0A2515C236B09DD@USALWEXMBX2.infor.com>
Date: Mon, 30 Sep 2013 12:30:59 -0500
Message-ID: 
 <CAOAgVpwMwWaC=+sUo3CitPKuo3DH2T13riSp1i=ZaQ+qAGx5fg@mail.gmail.com>
Subject: Re: Copy changes from one branch to another
From: Les Mikesell <lesmikesell@gmail.com>
To: Bob Archer <Bob.Archer@amsi.com>
Cc: Sven Richter <sveri80@googlemail.com>,
	"users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 30, 2013 at 12:13 PM, Bob Archer <Bob.Archer@amsi.com> wrote:
>>
>> But that has the effect that i will have all the changes from trunk in branch A,
>> which is not what I want. I only want some certain changes inside there, the
>> changes committed from our team.
>>
>
> Common stuff should be brought in with Externals rather than a merge. That may be a better use case considering what you are asking for.

Yes, if different teams are working on different components, using
externals is the way to go even if it takes some effort to arrange
things into neat subdirectories for easy reference.  Besides giving
you a way to pull in the changes cleanly, it also gives you a way to
version those points separately and each component can have its own
release/tagging process and the consuming projects can adjust their
references when they are ready.

-- 
    Les Mikesell
       lesmikesell@gmail.com