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

New git-rebase backend: no way to drop already-empty commits

From
Sami Boukortt <sami@boukortt.com>
Date
Apr 7, 2020, 16:30 UTC
Message-ID
<CAAb+AL8+c6knrQnoi7YOjyM+Wc8-rws-JXVufBc=PciAvPPFJQ@mail.gmail.com>
Hi,

Using git 2.26.0, I just tried using `git rebase` to strip empty commits from a branch, but it leaves them as-is, even with `--empty=drop`. With the “apply” backend, it removes them properly. Am I holding it wrong?

`git rebase -i` also doesn’t pre-comment them like it used to.
Thanks.

Best, Sami

Next: Elijah Newren
Message 1 of 10 in “New git-rebase backend: no way to drop already-empty commits”
  1. Sami BoukorttApr 7, 2020
  2. Elijah NewrenApr 7, 2020
  3. Sami BoukorttApr 7, 2020
  4. Elijah NewrenApr 7, 2020
  5. Sami BoukorttApr 7, 2020
  6. Elijah NewrenApr 7, 2020
  7. Junio C HamanoApr 7, 2020
  8. Bryan TurnerApr 7, 2020
  9. Elijah NewrenApr 7, 2020
  10. Junio C HamanoApr 7, 2020

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.