Re: [PATCH v2] revision: add --maximal-only option

> The merge-base --independent calculation is basically asking for
> the maximal set among commits in the intersection of two (or more)
> commit histories. One trick the merge-base calculation does is
> that it first looks for the --boundary commits, and then reduces
> from within that set. This avoid walking further into the history
> than necessary.
> ...
> And this would likely return the tips of the two branches, but
> also will detect if one already reaches the other or if one of
> 'main' or 'release' reaches one or both of them, excluding it
> from the maximal set.