From: Sergey Organov <sorganov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] t/t4013: add test for --diff-merges=off
Date: Mon, 17 Aug 2020 23:36:45 +0300 [thread overview]
Message-ID: <87wo1xko0y.fsf@osv.gnss.ru> (raw)
In-Reply-To: <xmqqr1s52nv5.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Mon, 17 Aug 2020 10:17:34 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Sergey Organov <sorganov@gmail.com> writes:
>
>> So, do these both effectively resolve to:
>>
>> git log -m --no-diff-merges --first-parent --patch
>>
>> where first -m is the one implied by --first-parent, ...
>
> Eh, why does --first-parent even affect the choice of -m/no-m when
> --no-diff-merges is explicitly given?
Well, let's try your question on 3 abstract options:
"Why does --X even affects the choice of --Y/no-Y when --Z is explicitly
given?"
And what is the assumed answer?
"--X should only affect the choice of --Y/no-Y when no --Z is explicitly
given"
right? Or, in other terms:
"--X implies --Y unless --Z is explicitly given (as opposed to implied?)"
Do you see the problem here? I do see this as a problem. Simple "--X
implies --Y" should be sufficient to achieve any of required behaviors.
No need for such complications.
I just try to figure if some more or less strict model is hidden behind
all this, and it seems there is none.
Thanks,
-- Sergey
prev parent reply other threads:[~2020-08-17 20:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 22:08 [PATCH 0/3] Change "--diff-merges" to require parameter Sergey Organov
2020-08-05 22:08 ` [PATCH 1/3] revision: change "--diff-merges" option " Sergey Organov
2020-08-05 22:08 ` [PATCH 2/3] doc/git-log: describe --diff-merges=off Sergey Organov
2020-08-12 0:06 ` Junio C Hamano
2020-08-12 0:48 ` Junio C Hamano
2020-08-12 8:08 ` Sergey Organov
2020-08-05 22:08 ` [PATCH 3/3] t/t4013: add test for --diff-merges=off Sergey Organov
2020-08-05 22:31 ` Junio C Hamano
2020-08-05 22:44 ` Sergey Organov
2020-08-05 23:19 ` Junio C Hamano
2020-08-05 23:44 ` Junio C Hamano
2020-08-06 8:34 ` Sergey Organov
2020-08-06 17:10 ` Junio C Hamano
2020-08-06 20:52 ` Sergey Organov
2020-08-07 23:11 ` Sergey Organov
2020-08-17 17:17 ` Junio C Hamano
2020-08-17 20:36 ` Sergey Organov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo1xko0y.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).