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

Re: AW: Timestamp issue with "svn status" in 1.9.3

From: Philip Martin <philip_at_codematters.co.uk>
Date: Fri, 04 Mar 2016 22:22:07 +0000

Peter Klotz <Peter.Klotz_at_ith-icoserve.com> writes:

> Instead of "why is the second change not reported" it should be "why
> is the first change reported".
>
> Relevant part of the script:

At this point Subversion has recorded a timestamp for the file.

> echo "2" > x
> touch -m -t "201212310000.00" x
> svn -q status <-- this change is detected by Subversion (why?)

The recorded timestamp is not 201212310000.00 so it does not match the
file's timestamp and Subversion detects the change.

> svn commit -m "" x

Subversion records the current timestamp 201212310000.00.

> echo "3" > x

The file's timestamp is not 201212310000.00 so it does not match the
recorded timestamp and Subversion detects the change.

> touch -m -t "201212310000.00" x
> svn -q status <-- this change is not detected by Subversion (as expected)

The recorded timestamp and the file's timestamp are both 201212310000.00
and Subversion does not detect the change.

-- 
Philip
Received on 2016-03-04 23:30:14 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.