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

[PATCH v2 0/2] ssh signing: fix merging signed tags & docs

From
Fabian Stelzer <fs@gigacodes.de>
Date
Oct 13, 2021, 07:51 UTC
Message-ID
<20211013075107.8584-1-fs@gigacodes.de>

Two small follow up patches on top of 1bfb57f642d. fmt-merge-msg needs to load gpg config to be able to verify merged tags. load it and add some tests. And i forgot to adjust the docs when we changed some behaviour of the original patch during review.

Sorry for sending this after the merge to next. I didn't want to send a full reroll of the big patch series for these small changes. Should i do that next time or can/should i send these to the list as single patches on top of my existing patch series? I used gitgitgadget for the series and i'm not sure how sth like this would work with it (if it does at all).

Fabian Stelzer (2):
  ssh signing: fmt-merge-msg tests & config parse
  ssh signing: clarify trustlevel usage in docs
 Documentation/config/gpg.txt |  4 +---
 fmt-merge-msg.c              |  6 ++++++
 t/t6200-fmt-merge-msg.sh     | 28 ++++++++++++++++++++++++++++
 3 files changed, 35 insertions(+), 3 deletions(-)
-- 
2.31.1
Next: Fabian Stelzer
Message 1 of 4 in “ssh signing: fix merging signed tags & docs”
  1. 0/2 ssh signing: fix merging signed tags & docsFabian Stelzer, Oct 13, 2021
  2. 1/2 ssh signing: fmt-merge-msg tests & config parseFabian Stelzer, Oct 13, 2021
  3. 2/2 ssh signing: clarify trustlevel usage in docsFabian Stelzer, Oct 13, 2021
  4. Junio C HamanoOct 13, 2021

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.