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

Re: [PATCHv2] push: heed user.signingkey for signed pushes

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 24, 2014, 16:49 UTC
Message-ID
<xmqqfvedh0pt.fsf@gitster.dls.corp.google.com>
In-Reply-To
<544A6A4C.4070704@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Ooops, I'm sorry. That must have sneaked in from running gpg with that
> home to see which keys we have in the test env. No change in trustdb
> intended. Probably gpg did some automatic trustdb recalculations, even
> though all I did was gpg --list-key.

OK, so it will be fine to queue the patch without the trustdb bits, I guess.

Thanks.
Previous: Michael J Gruber
Message 9 of 9 in “push: heed user.signingkey for signed pushes”
  1. push: heed user.signingkey for signed pushesMichael J Gruber, Oct 22, 2014
  2. [PATCHv2] push: heed user.signingkey for signed pushesMichael J Gruber, Oct 22, 2014
  3. Junio C HamanoOct 22, 2014
  4. Junio C HamanoOct 22, 2014
  5. Michael J GruberOct 24, 2014
  6. t/lib-gpg: make gpghome files writableMichael J Gruber, Oct 24, 2014
  7. Junio C HamanoOct 24, 2014
  8. Michael J GruberOct 24, 2014
  9. Junio C HamanoOct 24, 2014

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.