From: Kyle Meyer <kyle@kyleam.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Stephen Smith <ischis2@cox.net>, git <git@vger.kernel.org>,
Jeff King <peff@peff.org>
Subject: Re: SHA-256 transition
Date: Thu, 23 Jun 2022 20:29:27 -0400 [thread overview]
Message-ID: <8735fukioo.fsf@kyleam.com> (raw)
In-Reply-To: <220624.86fsjvj690.gmgdl@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason writes:
> E.g. I use magit with Emacs, and last I checked it would puke on
> SHA-256. But checking again it seems someone patched it in January of
> this year to e.g. change "{40}" in regexes to "{40,}", so in theory it
> should work now (but I didn't try actually using it in that mode).
Yeah, I gave it some testing as I made those adjustments [*], but "in
theory it should work" is about my level of confidence too. If you're
experimenting with SHA-256 repos and find spots where Magit chokes,
opening issues on Magit's side would be very appreciated.
[*] https://github.com/magit/magit/pull/4585
next prev parent reply other threads:[~2022-06-24 0:29 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
2022-06-23 22:21 ` Ævar Arnfjörð Bjarmason
2022-06-24 0:29 ` Kyle Meyer [this message]
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=8735fukioo.fsf@kyleam.com \
--to=kyle@kyleam.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.
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.