summaryrefslogtreecommitdiffstats
path: root/object-format-disclaimer.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-08-07 14:10:43 -0700
committerJunio C Hamano <gitster@pobox.com>2023-08-07 14:10:43 -0700
commitc237f228006138eb7f67f07a4022c7d1d2472d1b (patch)
treec16b5543f10d6e8487ddb8d94fae38a0fe682db9 /object-format-disclaimer.txt
parent62908fd797899ccb5145cff3b16cc206d83b9b3f (diff)
downloadgit-htmldocs-c237f228006138eb7f67f07a4022c7d1d2472d1b.tar.gz
Autogenerated HTML docs for v2.42.0-rc0-25-ga82fb6
Diffstat (limited to 'object-format-disclaimer.txt')
-rw-r--r--object-format-disclaimer.txt15
1 files changed, 9 insertions, 6 deletions
diff --git a/object-format-disclaimer.txt b/object-format-disclaimer.txt
index 4cb106f0d..e561e6668 100644
--- a/object-format-disclaimer.txt
+++ b/object-format-disclaimer.txt
@@ -1,6 +1,9 @@
-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: At present, there is no interoperability between SHA-256
+repositories and SHA-1 repositories.
+
+Historically, we warned that SHA-256 repositories may later need
+backward incompatible changes when we introduce such interoperability
+features. Today, we only expect compatible changes. Furthermore, if such
+changes prove to be necessary, it can be expected that SHA-256 repositories
+created with today's Git will be usable by future versions of Git
+without data loss.