On 20.12.2022 09:14, Evgeny Kotkov wrote:
2) We already need a working copy format bump for the pristines-on-demand
feature. So using that format bump to solve the SHA1 issue might reduce
the overall number of required bumps for users (assuming that we'll still
need to switch from SHA1 at some point later).
Using a new hashing algorithm in the working copy is relatively simple.
Making such a change backwards-compatible is not. It would be really
nice if this could be done in a way that allows newer clients to still
support older working copies without upgrading them; after all, we have
the infrastructure for this in place now.
-- Brane
