From: Fabian Stelzer <email@example.com> To: firstname.lastname@example.org Cc: Fabian Stelzer <email@example.com> Subject: [PATCH v2 0/2] ssh signing: fix merging signed tags & docs Date: Wed, 13 Oct 2021 09:51:05 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) 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 reply other threads:[~2021-10-13 7:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-13 7:51 Fabian Stelzer [this message] 2021-10-13 7:51 ` [PATCH v2 1/2] ssh signing: fmt-merge-msg tests & config parse Fabian Stelzer 2021-10-13 7:51 ` [PATCH v2 2/2] ssh signing: clarify trustlevel usage in docs Fabian Stelzer 2021-10-13 17:03 ` Junio C Hamano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v2 0/2] ssh signing: fix merging signed tags & docs' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).