> So, that's why you're seeing this behaviour. What's unclear is why you
are
> investigating this behaviour in the first place. What is your use case
for
> changing the file's content but leaving it's timestamp unchanged?
We have a very clear case for this.
An automated Jenkins process must e
On Thu, Sep 08, 2016 at 07:40:24AM -0700, xvdes...@gmail.com wrote:
> I believe the timestamp to have a granularity of minutes on Linux, but I'm
> not sure of this. Even if it has second precision, such merge scripts can
> beat that.
This depends on the file system being used. Microseconds are n
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
