On 14. 1. 26 21:58, Evgeny Kotkov via dev wrote:
Nathan Hartman<[email protected]> writes:
In the release notes for 1.15, I could draft some additional text to
document that when using a Pristines-on-Demand working copy, checksums
are relied on more strongly than with traditional, fully-cached working
copies. By documenting it, users can make a more informed decision as to
which kind of working copy is most appropriate for their use case.
Hi Nathan,
The actual behavior in trunk is same for all types of working copies —
they all use checksum comparison for the "is the file modified?" checks.
So currently there are no different modes, and a pristineless working copy
uses the exact same checksum comparison approach as a pristineful one.
With a fresh look, I think that in the current state we might want to
indeed have the full content comparison for pristineful working copies,
and only use checksum-based comparison for pristineless working copies
(as described in your response).
Didn't we have file size and modification time as additional checks if a
full-text compare was needed? The size is recorded in the wc-db and
should be even if the pristine file is absent, but the mtime is not,
IIRC. In any case, the more checks we use, the harder it is to construct
a collision.
-- Brane
