On 10.06.2011 20:41, Gerald Britton wrote:
> Hi -- I am trying to understand the difference in behavior between two flavors of Tortoise exports:
>
> 1. From Windows Explorer, I right-click on a working copy, select TortoiseSVN, then Export.
> - in the Export dialog, I type in a directory name. (e.g. C:\temp\) and click OK
> - After the export finishes, I look in C:\temp and there is my exported copy at C:\temp\myworkingcopy
> - sometime later, I want do do the export again.
> - this time, however, in the export dialog I navigate to C:\temp\myworkingcopy
> - I let the export run, but find that it has created a new subdirectory, c:\temp\myworkingcopy\myworkingcopy
>
> I was surprised by this. This is not how the subversion command line client works. If I did the same operation using the svn command:
> - svn export . c:\temp\myworkingcopy
>
> ...the first time, it creates the subdirectory "myworkingcopy". However, the second time, it warns me that the subdirectory is not empty and that I must use --force to overwrite the contents
>
> 2. I perform similar functions from the repository browser and find that it works like the svn command! It allows me to specify the destination directory and warns me when I am about to overwrite it.
>
> Is this correct behavior? At the least, I would expect that the context-menu export would work like the repo-browser export and also work like the svn command line client.
>
> As it is, I find it confusing, and hard to explain to my colleagues :(
Changed the behavior in r21553.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2762629
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-11 10:00:45 CEST