From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Stephen Smith" <ischis2@cox.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git <git@vger.kernel.org>, "Jeff King" <peff@peff.org>
Subject: Re: SHA-256 transition
Date: Thu, 23 Jun 2022 08:32:55 -0700 [thread overview]
Message-ID: <xmqqbkuj2y54.fsf@gitster.g> (raw)
In-Reply-To: <YrPFfk5eIX55oO8R@tapette.crustytoothpaste.net> (brian m. carlson's message of "Thu, 23 Jun 2022 01:44:30 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On 2022-06-23 at 00:45:40, Stephen Smith wrote:
>> 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?
>
> I'm hoping that my employer will give me time to work on this in the
> future. Perhaps I'll have more to show on this closer to the last
> quarter of the year.
>
> At the moment I happen to be very busy in my personal life, so I'm not
> finding a great deal of time to code much of anything. But if that
> changes, I'll try to get back to it.
Great ;-). Thanks.
next prev parent reply other threads:[~2022-06-23 15:35 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
2022-06-23 1:44 ` brian m. carlson
2022-06-23 15:32 ` Junio C Hamano [this message]
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
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=xmqqbkuj2y54.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=ischis2@cox.net \
--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.
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).