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

Re: Need clarification on when exactly TSVN detects that a file is "changed"

From: Greywolf <greywolf_at_starwolf.com>
Date: Sat, 15 Aug 2009 13:16:27 -0700 (PDT)

[Thus spake Stefan Küng ("SK: ") 8:36am...]

SK: > "Subversion determines whether a file has changed with the following
SK: > approach: has the 'last modification' date and/or the file size changed..."
SK: >

It has been my experience that if I overwrite a modified copy of a file
with a copy that is identical to the file BEFORE it was modified, TSVN
will think the file has not been modified (unless the svn:props are also

This is, to my mind, actually correct behaviour for a VCS -- if the
content of a file does not change by the time all is said and done,
irregarding modifications, there is really no point in checking it in.
If you need that mod time to be current because you're doing a build
or something, you should probably be fooling around with one of touching
the file that things depend on, removing the file that depends on
the file you've checked out, or setting TSVN checkouts not to use the
stored modification time.

[FYI: "date" and "time" as separate entities is an artifact of a bad
 design by Microsoft -- most sane utilities consider the date to be
 representative of the system time, and "last modification/access/change
 time" to be an absolute offset in seconds from Midnight 1 Jan 1970 GMT,
 thus including all aspects of time, i.e., year month day hour minute

 It doesn't help that Windows time zones are hard-clocked rather than
 calculated [i.e. changes in the timezone are directly written to the
 hardware clock], which is also brain-dead but that's a rant for another


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-15 22:16:36 CEST

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.