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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 12, 2021, 17:34 UTC
Message-ID
<xmqqv922405g.fsf@gitster.g>
In-Reply-To
<20211012092236.619822-1-fs@gigacodes.de>
Fabian Stelzer <fs@gigacodes.de> writes:
> 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.

Sigh, why does this series have to come _after_ the problematic commit that needs fixup! have finally hit 'next', after lingering in 'seen' for very long time, instead of much earlier?

In any case, the damage has been made. We don't revert a topic out of 'next' very lightly, so let's have the 'fixup!' one as a true incremental. We pretend as if we have already shipped what is in 'next' as part of a stable version to customers, and write a bugfix patch that says "Commit X made Y to do Z, which is wrong for such and such reasons. Make Y do W instead."

Thanks.
Previous: Junio C Hamano
Message 5 of 5 in “ssh signing: fix merging signed tags & docs”
  1. 0/2 ssh signing: fix merging signed tags & docsFabian Stelzer, Oct 12, 2021
  2. 1/2 ssh signing: fmt-merge-msg tests & config parseFabian Stelzer, Oct 12, 2021
  3. 2/2 fixup! ssh signing: verify signatures using ssh-keygenFabian Stelzer, Oct 12, 2021
  4. Junio C HamanoOct 12, 2021
  5. Junio C HamanoOct 12, 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.