Re: SHA256 support not experimental, or?
- From
Adam Majer <adamm@zombino.com>
- Date
- Jul 20, 2023, 15:07 UTC
- Message-ID
- <ZLlNtbAbVcYH7eFb@adams>
- In-Reply-To
- <2f5de416-04ba-c23d-1e0b-83bb655829a7@zombino.com>
I'll try again with inline patch. I think it wasn't picked up since it was mime encoded by the mail client..
- Adam
From 90be51143e741053390810720ba4a639c3b0b74c Mon Sep 17 00:00:00 2001 From: Adam Majer <adamm@zombino.com> Date: Wed, 28 Jun 2023 14:46:02 +0200 Subject: [PATCH] doc: sha256 is no longer experimental
The purpose of this patch is to remove scary wording that basically stops people using sha256 repositories not because of interoperability issues with sha1 repositories, but from fear that their work will suddenly become incompatible in some future version of git.
We should be clear that currently sha256 repositories will not work with sha1 repositories but stop the scary words.
Signed-off-by: Adam Majer <adamm@zombino.com> --- 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..666dbdb55c 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..1e976688be 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 repositories currently will not be able to share work +with "regular" SHA-1 repositories.
-- 2.41.0