Community
Participate
Working Groups
When double-clicking on a file in the file list, the behavior is strange in case of a merge commit: if compare mode is on, it shows a comparson of the ancestors of the merge commit; if compare mode is off, it shows the version of one (arbitrary?) ancestor of the merge commit. We need to think what to do here, as there is no unique ancestor available. Maybe we need to disable the double-click altogether?
Double click in compare mode should behave as git log -p -- <path>.
Code review at http://egit.eclipse.org/r/#change,1715
Merged as 7b31f66982887d3439365e14bcaa024bdd6a6d15