Simon Large wrote:
> 2008/9/2 Nathan Smith <nsmith_at_galileoprocessing.com>:
>
>> I do have a related question though. I really like Tortoise's diff and
>> merge interfaces, but I am also quite comfortable using the command line
>> for anything we need. I'm working on installing svn on the webserver to
>> facilitate quicker day-to-day operations. Right now I'm using Tortoise
>> with mapped drives to smba shares. In the configuration, it remembers
>> the 'Y' drive, not a path on the server. I can see some issues coming up
>> with different path names.
>>
>> Here's the question: How can I use both the command line and the mapped
>> drives on the same working copy? Does anyone know a good workaround?
>>
>
> You can use TortoiseSVN and the *Windows* command line client on the
> same working copy. You must not use the Linux command line client on
> the same working copy as TortoiseSVN. The working copy is assumed to
> be local and subversion does not guarantee compatibility between
> different OSs. You will end up with a broken WC if you do this.
>
> Simon
>
If there is a working copy incompatibility between OSs, that's too bad.
Is it too difficult to make WCs platform independent?
I suggest that at minimum, SVN clients are able to detect that a WC is
incompatible, and report a sensible error message, rather than giving
obscure behaviour and errors.
I suppose this suggestion should go to the SVN mailing list.
Regards,
Craig McQueen
Received on 2008-09-03 02:52:56 CEST