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

Re: No way to force checkin?...

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-10-29 10:43:02 CET

Peter Yamamoto wrote:
> use case: svn (1.3) apparently does not recognize some infected .exe
> files as different from the original.
> Hence, even if you have a clean version of the .exe, you cannot check it
> in!?
> is there any easy workaround? (I guess a rename operation? will that
> send content as well?).

Subversion is very smart and has detected that the files are infected.
That's why it won't allow you to commit the files. It protects itself
from getting infected stuff into its repository.

Ok, now the real reason:
Usually, when a file gets infected, the last-modified time is reset the
previous value by the virus so you won't detect the infection right
away. But Subversion only considers files as modified if the
last-modified time of a file differs from the one it has stored in the
BASE. If that time is different, then Subversion checks some more to
make sure the file is really modified. But if those times are identical,
it won't even check and just assume that the file was not modified.

(and no, I won't even ask why you would want to commit an exe in the
first place, and I don't wanna even know why you want to commit an
*infected* file)


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sun Oct 29 10:43:10 2006

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.