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

Re: Copy to working copy...

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-08-04 15:40:22 CEST

Duncan Booth wrote:
> Copy to working copy is behaving a bit strangely (this is with TortoiseSVN
> 1.3.5, Build 6804 - 32 Bit):
>
> I used the repo browser to select a file and then the
> 'Copy to working copy...' command.
>
> I get an alert titled 'Save as...' containing the text
> '<filename> already exists. Do you want to replace it?'
> so I clicked 'Yes'.
>
> I then get an error box: 'File <filename> already exists'
> with an OK button. (No, it isn't OK!)
>
> Why won't TortoiseSVN overwrite the file when I said it could replace it?
> The error message if I delete the target file first is a bit more useful:
> it then says 'Entry for <filename> exists (though the working file is
> missing)'.
>
> What I'm trying to do BTW (in case there is an easier way to achieve this)
> is to copy a much changed file from a different branch in place of the
> current working copy instead of trying to do a merge which will just get a
> lot of conflicts: is there an easier way to do that?

Use "Save as..." instead of "Copy to working copy". You want to replace
the file in the working copy with the one from the repository.

Or: delete the original file first (with TSVN, not just a windows
delete). Then the "copy to working copy" should work just fine.

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
Received on Fri Aug 4 15:40:42 2006

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

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