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

Re: [PATCH] #3807: 'svn up' of a nonexistent child in a copied dir triggers an assertion

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 23 Feb 2011 13:32:33 +0000

Daniel Shahaf <danielsh_at_elego.de> writes:

> ###: what *should* the 'svn up' do? Should it always succeed
> silently, or should

> ### 'svn cp A A2; svn mkdir ^/A/foo; svn up A2/foo' pull the new
> directory?

I don't think it should pull the new foo. At present "svn cp" fixes the
copyfrom revision and a subsequent "svn up" doesn't change it.

Having update change the copyfrom revision does look like a useful
feature, it's a way to resolve some tree conflicts, but I think we
should try for a full implementation rather than just a few corner

Received on 2011-02-23 14:33:16 CET

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