Stefan wrote:
>> Right. It seems that when merging into sparse working copy, the default
>> depth for svn.exe is not that of working copy, but rather that of the
>> immediate target (that is, "immediate children"). Presumably this is the
>> same on the API level as well, seeing the TSVN behavior.
>>
>> Other people are bumping into this as well, see e.g.
>>
>> http://svn.haxx.se/dev/archive-2009-03/0702.shtml
>>
>> on the SVN dev list. For the CLI, the workaround is to use explicit
>> "--depth=infinity".
>>
>> For a GUI client such as TSVN the issue is worse, as the GUI incorrectly
>> states that the merge depth is "working copy".
> Ahem: you can specify the depth in the merge dialog too.
Sure, that's what I've been doing with the sparse doc merges from /trunk to
/branches/1.6.x for example.
But my point was that it is misleading for the user with a sparse WC to see
depth "working copy" in the merge wizard. Why? Because it makes you think
that the merging will respect the sparse working copy depth, whereas in
reality it will only do it if you change the depth to "fully recursive".
Kari.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1405701
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-24 21:13:58 CET