Re: [RFC/PATCH 0/2] merge-base: add --merge-child option
- From
Kevin Bracey <kevin@bracey.fi>
- Date
- May 13, 2013, 14:26 UTC
- Message-ID
- <5190F806.6040207@bracey.fi>
- In-Reply-To
- <7vwqr3u9c5.fsf@alter.siamese.dyndns.org>
On 13/05/2013 01:22, Junio C Hamano wrote:
Show 12 quoted lines
> Kevin Bracey <kevin@bracey.fi> writes: > >> git log --ancestry-path --left-right E...F --not $(git merge-base >> --all E F) >> >> which looks like we're having to repeat ourselves because it's not >> paying attention... > You are half wrong; "--left-right" is about "do we show the </>/= > marker in the output?", so it is true that it does not make sense > without "...", but the reverse is not true: A...B does not and > should not imply --left-right. >
The repetition I meant is that by the definition of ancestry-path, the above would seem to be equivalent to
git log --ancestry-path --left-right E F --not $(git merge-base --all E F) $(git merge-base --all E F)
Anyway, revised separated-out version of the patch follows.
Kevin