We had an issue at our organization where changes were reverted when a user was merging his local repo with the remote repo changes. The merge conflicted and he unstaged all the changes that were not a conflict, he then resolved the conflict and added just the conflicted file and committed. The end result was that he reverted every change from his last pull of the remote to his merge point. The problem I'm having how hard it is to see this problem as both git show and git log on the merge commit do not show any reverted files. It was found by diffing his commit to each of the parents and seeing the opposite of what we expected in the patch output. Anybody have ideas how we can prevent these mistakes? While we are going to do more training, a hard stop that wouldn't even let these make it to remote would be preferred. I've done this using git add --interactive then reverting a files changes, though the actual crime was done using egit staging tool. It seems the command line won't let you unstage changes but gui tools and interactive tools seem to allow it. -- 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