commit: make sure we return all revisions expected by r1...r2 revspec
There was a case, found while writing gitaly comparison test for FindCommits (next patch) where current DAG logic missed some cset to include. r1...r2 revspec means, csets ancestor of r1 or r2, but not ancestor of both. Graph: D | \ B C | | | / A | O revspec: 'D...B' Expected revs: (D, C) Logic before this patch would return: (D,)
parent
160a2b68
No related branches found
No related tags found
Please register or sign in to comment