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

Re: [PATCH] Documentation: clarify signature verification

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 12, 2016, 15:48 UTC
Message-ID
<xmqqh9f6su8l.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160412010009.GD9034@hashbang.sh>
KellerFuchs <KellerFuchs@hashbang.sh> writes:
Show 10 quoted lines
> I would rather see something like
>
>>     Verify that the tip commit of the side branch being merged is
>>     signed with a valid key, i.e. a key that has a valid uid: in the
>>     default trust model, this means it has been signed by a trusted key.
>>     If the tip commit of the side branch is not signed with a valid key,
>>     the merge is aborted.
>
> It's unfortunately more verbose, but I don't want to make promises
> about GnuPG's behaviour that depends on the user's configuration.
Good thinking.  Thanks.
Previous: KellerFuchsNext: Fox in the shell
Message 6 of 7 in “Documentation: clarify signature verification”
  1. Documentation: clarify signature verificationThe Fox in the Shell, Apr 9, 2016
  2. Junio C HamanoApr 10, 2016
  3. KellerFuchsApr 11, 2016
  4. Junio C HamanoApr 11, 2016
  5. KellerFuchsApr 12, 2016
  6. Junio C HamanoApr 12, 2016
  7. Documentation: clarify signature verificationFox in the shell, May 13, 2016

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.