From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 26 Jul 2025 00:04:47 GMT
Subject: Re: Show skipped commit message after rebase conflict?
Message-ID: <xmqq5xff3jhc.fsf@gitster.g>
In-Reply-To: <CAAVFnN=S-bu1FNafyyH797AeBxUu+8vk5yJ5xaxCUBkBZin_6w@mail.gmail.com>

Cameron Steffen <cam.steffen94@gmail.com> writes:

>> But only if we can positively tell the reason why there is no change
> relative to the parent commit _is_ because the commit we are
> currently picking has already been applied, that is.
>
> I thought we merely would need to see that there are no staged changes
> to be committed, and there is a currently-picking commit that will now
> be skipped? I don't need to know whether the commit was already
> applied. I just want to know that the commit in the rebase plan is not
> being committed.

Then your earlier idea to reuse the same message

>> warning: skipped previously applied commit <hash>
>
> Potentially we could use the very same message.

would not work, would it?