git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFE] Teach hash-object to be able to choose signature types

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 19, 2019, 17:37 UTC
Message-ID
<xmqqmug5xdhm.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190817015123.GD365197@genre.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
Show 8 quoted lines
> trivial. I'm definitely not opposed if someone else is interested in
> picking it up or writing it; I don't believe my outstanding patches
> (which will likely show up on the list this weekend now that 2.23 is
> out) would affect it in any way.
>
> I'll try to push up the work that I'm doing into my "transition-interop"
> branch; it contains the work for literal hashing and a more significant
> refactor, which folks are free to ignore.
Thanks for pushing the SHA-256 transition forward.
Show 5 quoted lines
>
> The problem is somewhat ameliorated by the fact that for most projects,
> there will be a mapping between SHA-1 and SHA-256, so it'll be possible
> to look up between the two, but it can still be confusing if the "wrong"
> one appears in commit messages, say.
Previous: brian m. carlson
Message 3 of 3 in “[RFE] Teach hash-object to be able to choose signature types”
  1. Randall S. BeckerAug 16, 2019
  2. brian m. carlsonAug 17, 2019
  3. Junio C HamanoAug 19, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.