All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smith <ischis2@cox.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Stephen Smith" <ischis2@cox.net>, git <git@vger.kernel.org>,
	"Jeff King" <peff@peff.org>
Subject: Re: SHA-256 transition
Date: Wed, 22 Jun 2022 17:45:40 -0700	[thread overview]
Message-ID: <12092182.O9o76ZdvQC@thunderbird> (raw)
In-Reply-To: <YrI9dvfoc5NYgVDq@tapette.crustytoothpaste.net>

On Tuesday, June 21, 2022 5:29:59 PM MST brian m. carlson wrote:
> On 2022-06-21 at 10:25:01, Ævar Arnfjörð Bjarmason wrote:
> > But the reason I'd still say "no" on the technical/UX side is:
> >  * The inter-op between SHA-256 and SHA-1 repositories is still
> >  
> >    nonexistent, except for a one-off import. I.e. we don't have any
> >    graceful way to migrate an existing repository.
> 
> True, but that doesn't meant that new repositories couldn't use SHA-256.

So, any idea when a graceful way to migrate a repository might show up?

> 
> >  * For new repositories I think you'll probably want to eventually push
> >  
> >    it to one of the online git hosting providers, none of which (as far
> >    as I'm aware) support SHA-256 repos.
> 
> This, in my view, is the only compelling reason not to use it for new
> repositories.

Which is a reason to send patches by email. 





  reply	other threads:[~2022-06-23  0:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 22:51 SHA-256 transition Stephen Smith
2022-06-20 23:13 ` rsbecker
2022-06-21 10:25 ` Ævar Arnfjörð Bjarmason
2022-06-21 13:18   ` rsbecker
2022-06-21 18:14     ` Ævar Arnfjörð Bjarmason
2022-06-22  0:29   ` brian m. carlson
2022-06-23  0:45     ` Stephen Smith [this message]
2022-06-23  1:44       ` brian m. carlson
2022-06-23 15:32         ` Junio C Hamano
2022-06-23 22:21     ` Ævar Arnfjörð Bjarmason
2022-06-24  0:29       ` Kyle Meyer
2022-06-24  1:03       ` Stephen Smith
2022-06-24  1:19         ` Ævar Arnfjörð Bjarmason
2022-06-24 14:42           ` Jonathan Corbet
2022-06-24 10:52     ` Jeff King
2022-06-24 15:49       ` Ævar Arnfjörð Bjarmason
2022-06-25  8:53       ` brian m. carlson
2022-06-26  0:09         ` Plan for SHA-256 repos to support SHA-1? Eric W. Biederman
2022-06-26  0:27           ` Junio C Hamano
2022-06-26 15:19             ` brian m. carlson
2022-07-01 18:00         ` SHA-256 transition Jeff King

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=12092182.O9o76ZdvQC@thunderbird \
    --to=ischis2@cox.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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. 
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.