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

Re: Re: Is there really no way to keep the file modification time intact?

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-03-05 12:42:18 CET

On 3/5/07, Jan Hendrik <jan.hendrik@myrealbox.com> wrote:
> Concerning RE: Re: Is there really no way to
> Thompson, Graeme (AELE) wrote on 28 Feb 2007, 3:52, at least in
> part:
> > We have the constant argument that the modification date time is
> > unreliable, unfortunately this statement
> > is driven by programs like subversion that throw this information
> > away, thus making the modification date time unreliable.
> While at the same time relying on just this - and only on this - for
> commit!

Absolutely not!

Subversion has a heuristic to determine whether it may need to commit
a file or not. Loosing the mtime (ie damaging) is no problem for
subversion: the timestamp will have changed and this means the file
needs to be further inspected to see if a commit is required.

See, that's why Subversions behaviour isn't problematic from a 'mtime
is unreliable' pov: as soon as the mtime gets 'damaged', the file will
be further inspected. This means slowing down the commit, but nothing
more. 'Damaging' the mtime, as you can see, is not a problem for



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 5 12:43:04 2007

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

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