[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Managing Vendor Branches

From: Jeff Mott <jeff.mott.or_at_gmail.com>
Date: Sun, 28 Feb 2010 10:41:52 -0800

On Sun, Feb 28, 2010 at 4:28 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Sat, Feb 27, 2010 at 09:09:14PM -0800, Jeff Mott wrote:
>> I just discovered that using --ignore-ancestry fixed the problem. This
>> caused SVN to update rather than replace my working copy.
>
> What is the ancestral relationship between the branches containing
> the vendor drops? I assume they are just freshly imported directories?
>
> Stefan
>

Yes, they are freshly imported directories.

I found in the SVN book where this behavior is explained
(http://svnbook.red-bean.com/en/1.5/svn.branchmerge.advanced.html#svn.branchmerge.advanced.ancestry).
Fourth paragraph under the "Noticing or Ignoring Ancestry" section.

I only wish they mentioned all this in the Vendor Branches chapter.
Received on 2010-02-28 19:42:28 CET

This is an archived mail posted to the Subversion Users mailing list.