From: <rsbecker@nexbridge.com>
To: "'brian m. carlson'" <sandals@crustytoothpaste.net>,
"'Eric Wong'" <e@80x24.org>
Cc: <git@vger.kernel.org>
Subject: RE: any real-world SHA-256 repo users out there?
Date: Sun, 3 Apr 2022 13:55:45 -0400 [thread overview]
Message-ID: <02b501d84784$0e904260$2bb0c720$@nexbridge.com> (raw)
In-Reply-To: <Ykna7sJP8ktvNLor@camp.crustytoothpaste.net>
On April 3, 2022 1:36 PM, brian m. carlson wrote:
>On 2022-04-03 at 08:42:58, Eric Wong wrote:
>> Hey all, just wondering if it's something I should prioritize adding
>> support for in some git-using project I hack on...
>>
>> Of course, I'm not dropping SHA-1 support. So I'm wondering if I
>> should wait for (or hack on :P) git to handle both SHA-256 and
>> SHA-1 in one process; or if it's something I'd be better off managing
>> via multiple (git cat-file --batch) processes. No OIDs are
>> abbreviated, so it's just 20/40 vs 32/64.
>
>Git can already use one binary to handle SHA-1 and SHA-256 repositories and has
>been able to since Git 2.29 (although 2.30 has some fixes you should use). It just
>doesn't provide interop at this point, and I'm only working on it as I find time, so I
>wouldn't hold your breath for it.
>
>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.
>
>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?
Regards,
Randall
next prev parent reply other threads:[~2022-04-03 17:56 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 [this message]
2022-04-03 22:40 ` Junio C Hamano
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='02b501d84784$0e904260$2bb0c720$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--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.
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).