On Thu, Mar 3, 2011 at 08:42, Felix <fb_at_ltec.ch> wrote:
> On 03.03.2011 14:12, Jean-Marc van Leerdam wrote:
>> On 3 March 2011 13:59, Wolfgang Rohdewald<wolfgang_at_rohdewald.de> wrote:
>>> On Donnerstag 03 März 2011, Felix Saphir wrote:
>>>>> Can anybody give me hint about what I should try next,
>>>>> including changing a setting of the SAMBA server that is
>>>>> probably known to create trouble with Tortoise SVN?
>>>> Simple: Don't do that. Don't put working copies on network
>>>> shares and don't share working copies between operating
>>> I am doing that since a while now and I never had any
>>> problems at all. Mounting a windows 7 system on Linux
>>> and using Linux svn for manipulating the windows files.
>>> Same with sshfs for manipulating remote working
>>> directories over the internet - slow but no problems.
>>> So what are the risks? Are they Tortoise-specific?
>> The risks is: cross platform client interoperability is not guaranteed
>> by the subversion developers. Each platform has its own client
>> implementation and Working Copy formats are not necessarily the same.
> As I said: I do not share working copies between different platforms.
> They reside on a network share to make sure they get backed up. I do not
> use SVN as backup system and therefore some time my pass between two
> commits. During this time my working copy gets backed up daily.
If you insist upon keeping backups of your working copy, keep it
local, and schedule a task to copy it to your network location. But
don't continue using your WC on a network share after being told
repeatedly "don't do that" only to tell those same people you want it
fixed. You've been told about the problems. Either heed the advice
you've been given, or ignore it and live with the consequences.
> A real risk would be not to backup the working copy...
Only if you're not committing your changes to the repository regularly.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-03 14:47:39 CET