title: How to revert changes due to a merge with Eclipse and EGit
body: <p>I am using Eclipse Mars.1 (4.5.1) with EGit 4.1.0.</p>
  
  <p>After a merge from a branch into master, I cannot figure out how to tell EGit to resolve a conflict by simply keeping the version that was in master before the merge, ignoring anything that came into that file as a result of the merge.</p>
  
  <p>This is what I do. My Java projects all point to master. No uncommitted changes in any project.</p>
  
  <p>In Package Explorer view I right-click a project, click Team, Merge.</p>
  
  <p>In the "Merge 'master'" dialog that pops up I select a branch (under "Local"), I leave the "Merge options" on "Commit" and the "Fast forward options" on "If a fast-forward, only update the branch pointer".</p>
  
  <p>I click "Merge". The "Merge Result" dialog pops up and says "Result  Conflicting". Fair enough, I was expecting conflicts and I'm going to resolve them manually one by one.</p>
  
  <p>Now, my problem is that for some of the files in conflict the way I want to resolve the conflict is simply to reject any change to that file resulting from the merge; just keep that file as it was before I did the merge.
  This should be trivial to do (at least in SVN it was), but I cannot see anywhere in Eclipse how to do that. The merge has filled the file with the "&lt;&lt;&lt;&lt;&lt;&lt;" conflict markers and I just don't see what needs to be done to revert those changes <em>only in that file</em> so that that file simply becomes unchanged with respect to master, which is where all the projects are pointed.</p>
  
  <p>If I right-click on the file in the Synchronize view and select "Overwrite", I am asked if I "want to overwrite local changes". That's exactly what I want, I want the file to have no local changes, so I click Yes. But the result is that the file gets deleted locally, although it exists both in master and in the branch. It disappears from Package Explorer, and since I also had it open in the editor, that editor tab closes away. That's not what I meant by "overwrite local changes" and I don't understand why it happens.</p>
  
  <p>If instead of "Overwrite" I select "Mark as merged" (although the conflict markers are still there), the file is no longer shown as in conflict, but it still has all the conflict markers in it and of course is still shown as changed, while I want it to be unchanged with respect to master.</p>
  
  <p>And if instead I resolve all the conflicts in the other files and I want to commit all the files except the problematic one - so that that one will stay unchanged - when the commit dialog shows up and lists all the files to be committed, each with a checkbox, and I click on the checkbox of the problematic file to exclude it from the commit, the checkbox doesn't get unchecked, and this goes for any of the other files; the checkboxes don't look disabled, but they don't respond to the click.</p>
  
  <p>What am I missing ?</p>