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

Re: Tortoise does not set write permission after "get lock"?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sun, 20 Jan 2008 16:04:13 +0100

Holger Karl wrote:
>> It seems F-Secure also do a bad job here :-(
>> (And my employer force me to use F-Secure)
> [Holger Karl ]
> Which is really the point: corporate users usually do not have a choice
> here.
> How about adding this issue to the FAQ? It seems like it comes up
> occasionally.

That FAQ entry would need a title like "virus scanners are crap!" or
something like that. Because the issue with the readonly flag is not the
only one. Virus scanners interfere with network traffic (causing
corrupted data in the repository, errors while checking out, preventing
authentication, ...), they interfere with files (causing errors like
'can't move file' or 'file XXX locked' or others) when updating/checking
out, slow down the whole system ("commit takes 30 minutes for a 3kb
File!"), and they even 'readjust' the file modification time ("TSVN does
not recognize modified files").

Honestly: I'd rather catch a virus than install a virus scanner. A virus
at least tries to hide itself as best as possible, which means it
doesn't interfere or make my computer unusable.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-20 16:04:33 CET

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

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