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

git-rebase -i prunes commits with empty commit-message

From
Erik Faye-Lund <kusmabite@googlemail.com>
Date
Mar 8, 2010, 20:07 UTC
Message-ID
<40aa078e1003081207u20046916yda5a62d44ce7a401@mail.gmail.com>

I'm in the process of converting an SVN repo to Git, and in the process I found one quite disturbing feature of git-rebase--interactive.sh: It discards commits with empty commit messages!

Here's a recepie for reproducing the issue: --->8--- git init git commit -m "dummy" --allow-empty git commit -m "dummy" --allow-empty git commit -m "dummy" --allow-empty git filter-branch -f --msg-filter 'sed -e "s/dummy//"' git rebase -i HEAD~2 --->8---

The editor window will show "noop", and exiting the editor goes ahead and deletes all but the initial commit.

This gets even weirder if it's a mixture of empty and non-empty commits; the commit-identifiers gets appended, together with an angle-bracket ('>'), to the previous line.

I'm guessing that this is unintended behavior. This was observed on git 1.7.0.1.
-- 
Erik "kusma" Faye-Lund
Next: Michael Haggerty
Message 1 of 6 in “git-rebase -i prunes commits with empty commit-message”
  1. Erik Faye-LundMar 8, 2010
  2. Michael HaggertyMar 10, 2010
  3. Erik Faye-LundMar 10, 2010
  4. Erik Faye-LundMar 11, 2010
  5. Erik Faye-LundMar 11, 2010
  6. Junio C HamanoMar 10, 2010

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.