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

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

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Aug 16, 2019, 22:22 UTC
Message-ID
<009c01d55481$13d3ce20$3b7b6a60$@nexbridge.com>
Hi All,

I do not know whether this would be a good enhancement or micro project for someone (maybe me) to take on, but I'm wondering whether it might be a good idea to provide an option to hash-object to select the signature being computed. The use case begins when someone computes an object signature and stores a pre-converted SHA1 value. Then the repository is changed over to SHA256. When hash-object is next called, perhaps in a different clone or some other "next" scenario, the new signature will be SHA256, if I understand this correctly, and from the perspective of the someone in the use case, the signature mismatches.

What I am proposing is an option like --signature-type=SHA1|SHA256 or similar as an option to hash-object to allow the non-default signature to be selected explicitly. This is not entirely trivial looking through the code and presumably would require either teaching hash_object_file_literally or having a separate method to do the alternate calculation.

Thoughts? Regards, Randall

-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.
Next: brian m. carlson
Message 1 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.