Re: [PATCH v4 0/2] history: sign rewritten commits

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 2, 2026, 22:47 UTC
Message-ID: <xmqq7bjzvhxq.fsf@gitster.g>
In-Reply-To: <20261002132718.3830-1-git@5ouma.me>

Souma <git@5ouma.me> writes:

Show 5 quoted lines

> History rewriting creates commits through two paths: the history commands
> write replacement commits directly, while the replay machinery recreates
> descendants above the rewritten range. Neither path currently honors
> `commit.gpgSign` or an explicit signing request, so rewriting signed history
> can leave the resulting commits unsigned.

With this topic merged, 'seen' seems to break t9902.

Also, is this expected?

    $ git history split --git-completion-helper
    --update-refs= --dry-run --gpg-sign --no-dry-run -- --no-gpg-sign

$ 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.