2 ms·
I don't think it's that unreasonable to release git binaries today with sha256 support, then wait 5 years, then make all new commits use sha256. Anyone who tri
by londons_explore 7y ago
I don't think it's that unreasonable to release git binaries today with sha256 support, then wait 5 years, then make all new commits use sha256.
Anyone who tries to use a git client more than 5 years old wouldn't be able to pull+push to a new repo. Sounds reasonable to me. Git clients more than a few years old are pretty broken already due to TLS changes.
Keeping around a dual hash system forever sounds like baggage and complexity that outweighs the benefits.