On Thu, Jan 24, 2019 at 4:35 AM Jeff King <peff@xxxxxxxx> wrote: > Note that we have to tweak t4013's setup a bit to test this case, as the > existing merges do not have any --summary results against their first > parent. But since the merge at the tip of 'master' does add and remove > files with respect to the second parent, we can just make a reversed > doppelganger merge where the parents are swapped. ... > + # Same merge as master, but with parents reversed. Hide it in a > + # pseudo-ref to avoid impacting tests with --all. There are 2 calls with --all, which may be worth testing for as well assuming we still have similar bugs as shown in the second patch, but I guess this would also allow for other tests (how do we list all pseudo refs for example?) to cover more corner cases. I am not sure I like this.
