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

Re: [PATCH] tag: add tag.gpgSign config option to force all tags be GPG-signed

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 26, 2017, 20:55 UTC
Message-ID
<20171026205509.2ydjd3bai2l6pqxi@aiede.mtv.corp.google.com>
In-Reply-To
<20171026195516.3354-1-tigran.mkrtchyan@desy.de>
Hi,
Tigran Mkrtchyan wrote:
> In some workflows we have no control on how git command is executed,
> however a signed tags are required.

Don't leave me hanging: this leaves me super curious. Can you tell me more about these workflows?

Thanks and hope that helps, Jonathan

Previous: Tigran MkrtchyanNext: Mkrtchyan, Tigran
Message 2 of 7 in “tag: add tag.gpgSign config option to force all tags be GPG-signed”
  1. tag: add tag.gpgSign config option to force all tags be GPG-signedTigran Mkrtchyan, Oct 26, 2017
  2. Jonathan NiederOct 26, 2017
  3. Mkrtchyan, TigranOct 26, 2017
  4. Jonathan NiederOct 26, 2017
  5. Stefan BellerOct 26, 2017
  6. Mkrtchyan, TigranOct 27, 2017
  7. brian m. carlsonOct 28, 2017

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.