From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 02 Oct 2026 22:47:13 GMT
Subject: Re: [PATCH v4 0/2] history: sign rewritten commits
Message-ID: <xmqq7bjzvhxq.fsf@gitster.g>
In-Reply-To: <20261002132718.3830-1-git@5ouma.me>

Souma <git@5ouma.me> writes:

> 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