Erik Faye-Lund wrote: > 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--- Does git really claim to handle commits with empty commit messages? That you have to use git-filter-branch to create the test case suggests that the answer is "no", but I don't know. (git-commit, for example, refuses to create a commit with an empty message.) If indeed git requires commit messages to be non-empty, then the fault here seemingly lies with git-filter-branch for allowing commit messages to be completely deleted. Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html