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

Re: Strange diffs after rsync copying of working copy

From: Johan Holmberg <holmberg_at_iar.se>
Date: Fri, 03 Feb 2012 13:58:08 +0100

On 02/03/2012 01:28 PM, Stefan Sperling wrote:
> On Fri, Feb 03, 2012 at 12:47:57PM +0100, Johan Holmberg wrote:
>> Is Subversion really sensitive to such timestamp differences?
> Yes, it is. To avoid checking the entire content of all files in the
> working copy every time you run 'svn diff' or 'svn status', Subversion
> keeps a record of the timestamp each file had after checkout. If that
> timestamp differs from the one on disk, the file is considered modified.
>

But isn't this just a cache? If I do a "touch" on a file in my working
copy, "svn status" and "svn diff" does not report any new difference. I
guess the cached info is just invalidated, and "svn" has to re-calculate
the cached info. But there is still no difference introduced by a simple
timestamp change on a working copy file.

So I don't think saying "If that timestamp differs from the one on disk,
the file is considered modified." is correct. "svn" does not work like
that for me at least.

I'm beginning to suspect that the timestamps of files in the ".svn"
directory may matter, an cause the behaviour I described in my earlier mail.

/Johan Holmberg
Received on 2012-02-03 13:58:48 CET

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.