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

Modernise .gitconfig Signing Block Name

From
Aadmin@inferencium.net <admin@inferencium.net>
Date
Mar 2, 2024, 20:01 UTC
Message-ID
<KfyeAjLLXySd6IEKwEmOvrDqtBIhoCRPon7r8IuUIwPbUhlf8XR0CCmqP3Y5D-8hur57_SFQPqwk0xOA7p0h6xqw48ZMdNbzTBPN2hh9Ph4=@inferencium.net>
As SSH has been supported as a signing method for a while now in Git, the block name `gpg` within `.gitconfig` no longer makes sense as it's not the only method of signing commits and tags. I propose renaming `[gpg]` to something such as `[sig]` or `[sign]`. The current method of achieving this is `format = ssh` within the `[gpg]` block, which would be the same (hypothetically) as redefining SHA-1 to be SHA-256 via `format = sha256` within a `[sha1]` block; it really doesn't make sense in 2024 for it to be this way.
The outcome of this would be using `format = gpg` or `format = ssh` within a `[sig]` or `[sign]` block (or whatever anyone comes up with which could be better).
For backwards compatibility, `[gpg]` can also be allowed as an alias for the new name. The default could also be `format = gpg`, as it's still the most widely-used signing method.
Next: Junio C Hamano
Message 1 of 2 in “Modernise .gitconfig Signing Block Name”
  1. admin@inferencium.netMar 2, 2024
  2. Junio C HamanoMar 2, 2024

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.