On 6/29/23 07:59, Junio C Hamano wrote:
Adam Majer <adamm@xxxxxxxxxxx> writes:
Is sha256 still considered experimental or can it be assumed to be stable?
I do not think we would officially label SHA-256 support as "stable"
until we have good interoperability with SHA-1 repositories, but the
expectation is that we will make reasonable effort to keep migration
path for the current SHA-256 repositories, even if it turns out that
its on-disk format need to be updated, to keep the end-user data safe.
That could be a different definition of stable. But I'm satisfied that
current sha256 repositories will not end up incompatible with some
future version of git without migration path (talking about on-disk format).
So maybe my question should be reworded to "is sha256 still considered
early stage, for testing purposes only with possible data-loss or can it
be relied on for actual long lived repositories?"
So while "no-longer-experimental" patch is probably a bit premature,
the warning in flashing red letters to caution against any use other
than testing may want to be toned down.
Agreed. I think it should be clear that SHA256 and SHA1 repositories
cannot share data at this point. The scary wording should be removed
though, as currently it sounds like "data loss incoming and it's your
fault" if one chooses sha256
- Adam
