Re: [TSVN] Bug in repo browser > "Copy to working copy"

Nick Gilbert wrote:

> I think I've found a bug in the repo browser. I'm trying to update a
> binary file in my working copy to a previous version.
>
> In the repo browser, I right clicked the file and choose "Save to
> working copy". I chose the file in my working copy I wanted to overwrite
> it with (the same file) and it asks "blah already exists, do you want
> to overwrite?" So I click "yes". It then gives an error telling me it
> already exists. It's already told me that and asked if I want to
> overwrite it so it should go ahead and replace the file :)

Right.
Fixed in revision 3162.

> Secondly - a question:
>
> What is the difference between "Save as" and "Copy to working copy"
> (apart from the fact that save-as can overwrite files)? They seem to be
> the same. I expected "copy to working copy" to give me a save file
> dialog that was already looking at my working copy folder, but it
> doesn't - it defaults to My Documents or something (as does save-as) so
> what's the difference?

"Save as..." overwrites the file if it exists or creates a new,
unversioned one.
"Copy to working copy" does the same, but it keeps the file history.
That means if you copy the file to a new location in your working copy,
it becomes versioned and in the log of that file you'll see 'copied from
/trunk/file1 : revision XXX'. The same applies if you overwrite an
existing versioned file - the log then shows you a 'copied from' there too.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org