Quoting Mark Blakeney <markb@xxxxxxxxxx> > Surely something like an option --allow-empty on the rebase -i to skip over > these no-brainer picks is trivial to implement - and makes sense? As a simple > user, and knowing the original commits required --allow-empty, it was the first > option I went looking for on the rebase -i when I encountered this problem. I think an alternative is to use 'git rebase --skip'. I don't understand why you can't get rid of the commits that don't do anything and serve no purpose once and for all. In your first message you only said 'for various reasons' and it isn't clear why you need such empty commits. Often people say they want to add a comment about the state of the tree with empty commits, but tags are designed for that purpose. Unlike some other systems a tag can have a message of its own. -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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