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

Re: [PATCH v2] rebase -i: reword empty commit after fast-forward

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 11, 2025, 17:51 UTC
Message-ID
<xmqq8qqcz7wk.fsf@gitster.g>
In-Reply-To
<pull.1860.v2.git.1739289549299.gitgitgadget@gmail.com>
"Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com> writes:
> As "git commit" will happily create empty merge commits without
> "--allow-empty" we do not need to pass that flag when rewording merge
> commits.
Thanks, will queue.  Let's mark it for 'next'.
Previous: Phillip Wood via GitGitGadget
Message 4 of 4 in “rebase -i: reword empty commit after fast-forward”
  1. rebase -i: reword empty commit after fast-forwardPhillip Wood via GitGitGadget, Feb 5, 2025
  2. Junio C HamanoFeb 5, 2025
  3. rebase -i: reword empty commit after fast-forwardPhillip Wood via GitGitGadget, Feb 11, 2025
  4. Junio C HamanoFeb 11, 2025

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.