Jakub Narebski <jnareb@xxxxxxxxx> writes: [...] > 3. Now, if you have published 1..5 history you would not want > (usually) to rewind published branch. If you do the following: > > $ git revert --no-commit 5 the working tree in now dirty... > $ git revert 4 and this one fails with dirty tree :( Probably: $ git revert -n 5 && git revert -n 4 && git commit -a BTW, why git-revert doesn't take a range? Is there some fundamental problem with it? -- Sergei. -- 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
