Fix "Conflicts With" when current change is a merge commit
The "Conflicts With" for a change which itself is a merge commit wasn't
computed properly because the list of affected files by the merge-commit
is either empty or contains only those files where conflicts where
resolved. Because of that, only few other changes had an overlap over
the affected files and only those changes where considered as the
candidates for the "Conflicts With" list.
To make this work we need to compute the list of affected files
properly. Taking an example of an open change which is a merge:
master > o
|
o o Change-123
| /|
merge-base > o o (changes a.java)
| /
o
to compute the set of affected files by the Change-123 relative to its
target branch (master) we take the list of files which is different
between the merge-base and the Change-123. In this example the
file a.java will be included in the list of affected files.
Bug: issue 3052
Change-Id: Ic20ea9c348f78a2dfca2448346a7719b7937eef2
1 file changed
