R. Tyler Ballance schrieb: > The most common use-case involves a user merging a project branch into a > stabilization branch (`git checkout stable && git pull . project`) in > such a way that no merge commit is generated. Of course, without > thinking they'll push these changes up to the centralized repository. > Not 15 minutes later they realize "ruh roh! I didn't want to do that" > and become very frustrated that they have to resort to asking for help > or hand-reverting N number of commits. Is the problem * that there is no merge commit, or * that you have to undo N commits instead of just one? The latter is probably helped by $ git reset --hard ORIG_HEAD && git push -f origin -- Hannes -- 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
