Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 4 Jun 2013 18:42:47 +0200
From: Andreas Krey <a.krey@gmx.de>
To: "Saffer, Simon" <simon.saffer@cgi.com>
Cc: "C. Michael Pilato" <cmpilato@collab.net>,
   "users@subversion.apache.org" <users@subversion.apache.org>
Subject: Re: Lines duplicated in dest. file when merging back to trunk
Message-ID: <20130604164247.GI22784@inner.h.apk.li>
References: <86FB15D93A38CB459D7A270423145743029A9A@SE-EX028.groupinfra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86FB15D93A38CB459D7A270423145743029A9A@SE-EX028.groupinfra.com>
User-Agent: Mutt/1.4.2.1i

On Tue, 04 Jun 2013 14:09:35 +0000, Saffer, Simon wrote:
...
> 
> A
> B
>    
>    some change
>    
>    some change
>    
> C
> D
> 
> We get no merge conflict, but the text is copied twice into the file on trunk.

So, you add one line on trunk, and a different line (and different
whitespace mieans 'different') on the branch, and you expect the
VCS to drop one of them?

It is obvious that both changes should be taken into the merge,
arguably (and usually) unless they are exactly the same, so SVN
does nothing wrong here.

The more interesting part is why you don't even get a conflict.
Apparently the exact place you do the modification in are also far
enough apart from each other so that the merge algorithm can take
them as independent chunks that affect disjunct parts of the original
file.

You should really go and cherry-pick such changes from one branch
to the other.

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800