Re: [PATCH v2 0/7] making log --first-parent imply -m
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 5, 2020, 19:24 UTC
- Message-ID
- <xmqqsgd0opzd.fsf@gitster.c.googlers.com>
- In-Reply-To
- <87d045nfju.fsf@osv.gnss.ru>
Sergey Organov <sorganov@gmail.com> writes:
> Yes, we can invent the rule that implied options don't ...
"invent"? It is nothing new, isn't it? IIRC, Peff's "first-parent implies 'm' but can be countermanded with --no-diff-merges" defines "implication" exactly that way. I do not think that is a recent invention but it is just following the patterns set by other options that has conditional implications.
IOW,
$ git log --no-diff-merges --first-parent -p next $ git log --first-parent -p --no-diff-merges next
should both mean the same thing. The user said no patch is wanted for merge commits with --no-diff-merges and --first-parent does not affect it.