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

Re: Git uses wrong subkey for signing commits with GPG key

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 16, 2018, 18:23 UTC
Message-ID
<xmqqlggxvf1c.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20180113172555.GS29313@zaya.teonanacatl.net>
Todd Zullinger <tmz@pobox.com> writes:
Show 10 quoted lines
> Glad it helped.  The git-tag documentation points to
> git-config and the user.signingKey variable in the
> CONFIGURATION section.  The git-config documentation for
> that variable currently says:
> ...
>     so you may specify a key using any method that gpg supports.
>
> Whether that can be improved without being too verbose (or
> duplicating too much of the gpg documentation), I don't
> know.

Yeah, I personally do not want to see Git's documentation sound more autoritative than it actually is wrt how to use software from other people, especially given that we do not have volunteers who will closely be keeping track of their changes in order to update our documentation. So "any method that gpg supports" is a good place to stop from that point of view. "See documentation for the version of PGP software you use for details." is not a bad thing to add without risking to go stale, though.

Previous: Todd Zullinger
Message 5 of 5 in “Git uses wrong subkey for signing commits with GPG key”
  1. Andrzej OśmiałowskiJan 13, 2018
  2. Todd ZullingerJan 13, 2018
  3. Andrzej OśmiałowskiJan 13, 2018
  4. Todd ZullingerJan 13, 2018
  5. Junio C HamanoJan 16, 2018

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.