On Wed, Oct 29, 2025 at 09:27:52AM +0100, Kornel Benko wrote: > Am Wed, 29 Oct 2025 08:11:09 +0000 > schrieb Kornel Benko <[email protected]>: > > > commit 735b747dbe317540d6121d8f63b70cf1c8895695 > > Author: Kornel Benko <[email protected]> > > Date: Wed Oct 29 09:08:52 2025 +0100 > > > > Amend ee65f260 > > > > Compilation with clang emits new warning (cast-align) > > This should have been 'Amend db0a86e6' > > How can I modify the log entry?
You would need to force push, since the log entry is part of the commit. Every project has different policies about force push. My personal opinion in this case would be to not force push. The mistake is fine. Or if you want, you can write an *empty* follow-up commit, e.g., "git commit --allow-empty" in which there is no diff but your message can say "amend 735b747d" and you write your amended log entry. i.e., you are amending the log entry (which is part of the commit). The above is completely my personal opinion. I am not aware of what official guides suggest in this case, or project policies. I'm curious what others suggest. Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
