git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: git@vger.kernel.org
Subject: any real-world SHA-256 repo users out there?
Date: Sun, 3 Apr 2022 08:42:58 +0000	[thread overview]
Message-ID: <20220403084258.GA27999@dcvr> (raw)

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.

I actually started an entirely new project in May 2021 using
SHA-256 and the only problem I've encountered (now fixed) was
with HTTP(S) clones.  I still haven't publicized that new
project, yet (I keep getting brain farts and side-tracked with
other stuff...)

             reply	other threads:[~2022-04-03  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03  8:42 Eric Wong [this message]
2022-04-03 17:35 ` any real-world SHA-256 repo users out there? brian m. carlson
2022-04-03 17:55   ` rsbecker
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=20220403084258.GA27999@dcvr \
    --to=e@80x24.org \
    --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).