From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'brian m. carlson'" <sandals@crustytoothpaste.net>,
"'Eric Wong'" <e@80x24.org>, <git@vger.kernel.org>
Subject: Re: any real-world SHA-256 repo users out there?
Date: Sun, 03 Apr 2022 15:40:07 -0700 [thread overview]
Message-ID: <xmqqa6d1u6yg.fsf@gitster.g> (raw)
In-Reply-To: <02b501d84784$0e904260$2bb0c720$@nexbridge.com> (rsbecker@nexbridge.com's message of "Sun, 3 Apr 2022 13:55:45 -0400")
<rsbecker@nexbridge.com> writes:
>>I have some indefinite plans to improve the support for
>>SHA-1/SHA-256 interop in the future, as well as port SHA-256
>>support to libgit2, but those are dependent on some things which
>>are not certain (but very likely) to occur.
That is encouraging to hear.
SHA-256 interop is one of the things I want to see appear sooner
rather than later (it would be what I would answer to the popular
"Git Rev News" question, if I were interviewed). I certainly would
want it to materialize before I retire ;-)
>>I strongly encourage folks to add SHA-256 repository support to
>>tooling since it's likely going to become more popular in the
>>future. I have some local SHA-256 repositories on my systems and
>>they appear to work fine.
>
> Our tooling works correctly regardless of the choice of SHA-256,
> but have been waiting for GitHub et. al., to provide
> capabilities. I would welcome interoperability. What help do you
> need?
prev parent reply other threads:[~2022-04-03 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 8:42 any real-world SHA-256 repo users out there? Eric Wong
2022-04-03 17:35 ` brian m. carlson
2022-04-03 17:55 ` rsbecker
2022-04-03 22:40 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa6d1u6yg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
--cc=sandals@crustytoothpaste.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.