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

Re: Copy/move-handling on update in 1.5

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-11-14 17:49:06 CET

On 11/14/07, Tor Ringstad <torhr@pvv.org> wrote:
> There are a few caveats: [...] Also, if an incoming move-operation
> deletes 'foo' before it attempts to copy it to 'bar', then the copy
> will fail, and the client reverts to the old behavior of fetching a
> pristine copy of the file from the repository.
> Is this what hits me? I can see (note #1) that the delete appears to
> happen before the copy. Is this what the caveat is talking about?


> In that case, is there actually any situation where the *user* will
> notice any improvements with regard to copy/move-handling on update?

Yes. When the file is copied before it is deleted. I am not sure if
this is predictable via filename. You could do:

svn mv file2 afile2

And see if that is different.

Moving a file from a subdir into its parent should do it.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 14 17:49:18 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.