Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
From: Philip Martin <philip.martin@wandisco.com>
To: Peter Klotz <Peter.Klotz@ith-icoserve.com>
Cc: "users\@subversion.apache.org" <users@subversion.apache.org>,
  Jonathan Komar <Jonathan.Komar@ith-icoserve.com>
Subject: Re: Timestamp issue with "svn status" in 1.9.3
References: 
 <FDCF7296051FAA4B967818014FE88B23023F6551BF7C@hermes.ith-icoserve.com>
Date: Fri, 04 Mar 2016 15:27:40 +0000
In-Reply-To: 
 <FDCF7296051FAA4B967818014FE88B23023F6551BF7C@hermes.ith-icoserve.com>
	(Peter Klotz's message of "Fri, 4 Mar 2016 12:54:42 +0100")
Message-ID: <874mcmi7pv.fsf@wandisco.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Peter Klotz <Peter.Klotz@ith-icoserve.com> writes:

> When changing the timestamp of a file to an earlier point in time and
> leaving the file size unchanged yet altering the content, Subversion
> is not always able to detect this change.

Not any earlier time, but only the exact earlier time at which
Subversion wrote an unchanged file.  Without this optimisation
large working copies would be extremely slow.

$ svnadmin create repo
$ svnmucc -mm -U file://`pwd`/repo put <(echo xx) f
$ svn co file://`pwd`/repo wc
$ stat wc/f | grep Modify
Modify: 2016-03-04 15:15:25.927354821 +0000
$ echo zz > wc/f
$ svn st wc           # timestamp younger so modification detected
M       wc/f
$ touch -d '2016-03-04 15:15' wc/f
$ svn st wc           # timestamp older so modification detected
M       wc/f
$ touch -d '2016-03-04 15:15:25.927354821' wc/f
$ svn st wc           # timestamp equal so modification not detected
$ 


-- 
Philip Martin
WANdisco