From: Junio C Hamano <gitster@pobox.com>
To: Adam Majer <adamm@zombino.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: sha256 is no longer experimental
Date: Mon, 31 Jul 2023 09:01:10 -0700 [thread overview]
Message-ID: <xmqqr0ooyss9.fsf@gitster.g> (raw)
In-Reply-To: <ZMe6KmzZGVubYpvO@adams> (Adam Majer's message of "Mon, 31 Jul 2023 15:42:02 +0200")
Adam Majer <adamm@zombino.com> writes:
> +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 expected that SHA-256 repositories
"can BE expected" (will tweak locally while queueing; no need to resend).
> +created with today's Git will be usable by future versions of Git
> +without data loss.
Will queue. Thanks!
next prev parent reply other threads:[~2023-07-31 16:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 16:28 SHA256 support not experimental, or? Adam Majer
2023-06-29 1:59 ` brian m. carlson
2023-06-29 10:42 ` Adam Majer
2023-06-29 5:59 ` Junio C Hamano
2023-06-29 10:53 ` Adam Majer
2023-06-29 20:56 ` Junio C Hamano
2023-06-29 21:17 ` brian m. carlson
2023-06-29 22:22 ` Junio C Hamano
2023-06-30 1:21 ` brian m. carlson
2023-06-30 9:31 ` Patrick Steinhardt
2023-06-30 11:25 ` Adam Majer
2023-06-30 11:38 ` Patrick Steinhardt
2023-06-30 12:20 ` Son Luong Ngoc
2023-06-30 16:45 ` Junio C Hamano
2023-07-20 15:07 ` Adam Majer
2023-07-20 18:18 ` Junio C Hamano
2023-07-26 16:44 ` Junio C Hamano
2023-07-31 13:38 ` Adam Majer
2023-07-31 13:42 ` [PATCH] doc: sha256 is no longer experimental Adam Majer
2023-07-31 16:01 ` Junio C Hamano [this message]
2023-07-31 16:44 ` Adam Majer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr0ooyss9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adamm@zombino.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).