Hi -
On 10/07/2025 19:36, Branko Čibej wrote:
On 10. 7. 25 17:37, Johan Corveleyn wrote:
In general, the file in your $broken_workingcopy might have been
changed out-of-band, by some other tool, a virus, a disk failure, ...
but the main question is: why doesn't your $broken_workingcopy detect
that it's modified?
Is that a correct rephrasing of your question?
Subversion uses a shortcut when detecting changed files in the working
copy: if the file's size is the same size as recorded in the metadata,
and its modification time is the same as that recorded in the
metadata, svn assumes the file did not change.
Interesting - so it's like the default rsync opts. I can (almost)
understand 'svn status' doing this, but surely 'svn diff' should
actually carry out a byte-by-byte comparison if the sizes are the same?
This is Ubuntu 22.04, on an HPE ProLiant ML30 Gen30. Sadly, product
quality fell off a cliff when HP sold their PC line to HPE, so the root
cause was almost certainly a memory failure. The server's going in the
bin when I can find something else.
