Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
From: Philip Martin <philip.martin@wandisco.com>
To: Johan Holmberg <holmberg@iar.se>
Cc: "users\@subversion.apache.org" <users@subversion.apache.org>
Subject: Re: Strange diffs after rsync copying of  working copy
References: <4F2BC96D.2020902@iar.se> <20120203122811.GB18533@ted.stsp.name>
	<4F2BD9E0.2070809@iar.se> <87wr84kqs1.fsf@stat.home.lan>
	<4F2BE1AA.8040409@iar.se>
Date: Fri, 03 Feb 2012 13:50:36 +0000
In-Reply-To: <4F2BE1AA.8040409@iar.se> (Johan Holmberg's message of "Fri, 03
	Feb 2012 14:31:22 +0100")
Message-ID: <87liokkour.fsf@stat.home.lan>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Johan Holmberg <holmberg@iar.se> writes:

> On 02/03/2012 02:09 PM, Philip Martin wrote:
>> Johan Holmberg<holmberg@iar.se>  writes:
>>
>>> 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.
>> You are correct, that is not how Subversion behaves.  Subversion checks
>> the timestamp to determine whether to do a full text comparison.  If the
>> timestamp and size of a working file match the recorded values the file
>> is assummed to be unmodified.  If the values differ Subversion does a
>> full text comparison to determine if the files differ.
>>
>
> I have now done some further experiments. I just issued commands like this:
>
>     $ svn status              # no modified files reported

Subversion is not doing a full text comparison because the timestamps
match.  So the difference that is present is not reported.

>     $ touch foo.txt bar.txt

Now the timestamps don't match.

>     $ svn status
>     M       foo.txt <------ only "foo.txt" not "bar.txt"

Subversion now does a full text comparison and the difference is
identified.


-- 
Philip