It was 1.8.14 client.
It just said "Reverted " and the subsequent "svn status" made no
mention of the . Brent
From: Johan Corveleyn
To: webster.br...@rogers.com
Cc: "users@subversion.apache.org"
Sent: Thursday, March 3, 2016 3:29 AM
Subject: Re: Weird Behaviour: Files reverted th
Peter Klotz 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 "20121231.00" x
> svn -q status <-
Hello Stefan
Thank you for the quick and detailed response.
> > 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.
> > The attached test case is the simplest we co
Peter Klotz 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 unchan
On Fri, Mar 04, 2016 at 12:54:42PM +0100, Peter Klotz wrote:
> Hello Subversion Developers
>
> We encountered a strange issue with Subversion 1.9.3 (running under RHEL 7).
> The attached script demonstrates the behavior.
>
> When changing the timestamp of a file to an earlier point in time and l
Hello Subversion Developers
We encountered a strange issue with Subversion 1.9.3 (running under RHEL 7).
The attached script demonstrates the behavior.
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 n
