These patches allow a --dirty option for git-rebase, git-rebase--interactive, and git-svn rebase. When --dirty is given, starting from a dirty tree state will be allowed. The difference between HEAD and the index and between the index and the working tree will be committed, these commits will be undone when the rebase is completed. For me the most often used use case is git-svn rebase one, which i use often. This prevents me form having to commit+reset or stash+unstash everytime i want to do this in a dirty tree. I recently saw some discussion about a stash-based patch to do the same thing, and decided to share this. These patches are a bit rough in some places, and mostly meant to see what others think if this way of doing this. One advantage above using stash is that merge conflicts will be presented to the user in the same way as when doing a normal rebase. Also having to explicitly ask for this behaviour with --dirty will hopefully give the user some clue that this isn't a standard operation. But, in the rebase--interactive case, it allows the user to shoot himself in the foot by re-ordering the commits such that the temporary ones aren't at the end anymore. Well, comments are welcome :-) - 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
