Re: Tortoise SVN having hernias over existing local copies.

Warren Kinny wrote:
> 1) If Tortoise can happily merge changes into existing files, and
> identify potential conflicts etc, why on new items can't it just say
> "OK, that file is already there and is identical" or bypass it, or
> warn and keep going ? WHY does it abort the download process ?
> Isn't this a BUG / unnecessary limitation ??

That is subversion behaviour, not TSVN. Nothing we can do about that.
Subversion will never overwrite a local unversioned file with a
versioned one because it could be overwriting something important that
just happens to have the same name. It *could* check to see if the
content is identical, but doesn't do so at the moment.

> 2) Is there anything that can be done to fix the pickle without
> having to delete the whole directory and check-out again ?
>
> 3) Are we missing the basic boat here ? Is tortoise designed to cope
> with the basic situation of BOTH development teams having full local
> copies ? Are we procedurally missing something very basic ? It seems
> that we are constantly running into problems with the tool in the way
> that we are trying to use it.. that suggests to me that we are not
> using it correctly, or it is not the correct tool for the situation
> we face.

Why on earth are you emailing source files to each other. The idea is
that team A makes a change and commits it. Team B does an update and
receives the change from the repository. Communicate changes through the
repository. Trying to bypass the repository is what is causing you the
problem.

Simon

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