SHA256 support not experimental, or?
- From
Adam Majer <adamm@zombino.com>
- Date
- Jun 28, 2023, 16:28 UTC
- Message-ID
- <2f5de416-04ba-c23d-1e0b-83bb655829a7@zombino.com>
Hi all,
Is sha256 still considered experimental or can it be assumed to be stable?
The usecase here is we are planning on moving to sha256 repositories mostly due to integrity guarantees, hypothetical or otherwise. What is important is not the initial interop challenges with sha1 repos, but whether the on-disk format will remain compatible with future versions of git. At minimum, the on-disk format would be converted by some future version(s) of git into another one and not be an end-of-the-road because it was "experimental" where dataloss is an implied risk.
Attached is a patch that removes the scary text, if indeed sha256 should be viewed as stable.
Cheers, - Adam
--- Documentation/git.txt | 4 ++-- Documentation/object-format-disclaimer.txt | 8 ++------ 2 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt index f0cafa2290..7c150a473c 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -553,8 +553,8 @@ double-quotes and respecting backslash escapes. E.g., the value If this variable is set, the default hash algorithm for new repositories will be set to this value. This value is ignored when cloning and the setting of the remote repository - is always used. The default is "sha1". THIS VARIABLE IS - EXPERIMENTAL! See `--object-format` in linkgit:git-init[1]. + is always used. The default is "sha1". + See `--object-format` in linkgit:git-init[1]. Git Commits ~~~~~~~~~~~ diff --git a/Documentation/object-format-disclaimer.txt b/Documentation/object-format-disclaimer.txt index 4cb106f0d1..dccee9c400 100644 --- a/Documentation/object-format-disclaimer.txt +++ b/Documentation/object-format-disclaimer.txt @@ -1,6 +1,2 @@ -THIS OPTION IS EXPERIMENTAL! SHA-256 support is experimental and still -in an early stage. A SHA-256 repository will in general not be able to -share work with "regular" SHA-1 repositories. It should be assumed -that, e.g., Git internal file formats in relation to SHA-256 -repositories may change in backwards-incompatible ways. Only use -`--object-format=sha256` for testing purposes. +Note: SHA-256 repository will in general not be able to +share work with "regular" SHA-1 repositories.
-- 2.41.0