I am new to git but think I have found a bug. I searched the git archives and found the same issue reported by Michael Gruber about 1 year ago but it was discounted by Stephan Beyer and the problem seems to be forgotten about. See http://kerneltrap.org/mailarchive/git/2008/7/8/2388804 In short, I think git rebase needs a "--allow-empty" option. I have git repo which I converted from an old system and which for various reasons requires me to --allow-empty commits when I build it. The repo has about 3300 commits but now when I try to fix up some of the early commit comments using git rebase -i I find I have to manually sit at the terminal and dumbly type; git commit --allow-empty (then quit out of editor) git rebase --continue ad nauseum for all the many empty commits ... I'm only rebasing to change some commit messages which must be a trivial git operation. Surely git rebase -i should be able to be told to continue through empty commits itself? At the very least some kind of message to the user would help - I only found that git commit --allow-empty works around this rebase problem once I found the old post above. I am using the latest version 1.6.3.3 of git. This is the version used to build the repo from scratch and for the git rebase -i etc. -- Mark Blakeney -- 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