git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: "Érico Rolim" <erico.erc@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG] In git-log, --name-status flag overrides the --patch flag
Date: Mon, 21 Dec 2020 11:09:58 -0800	[thread overview]
Message-ID: <xmqq5z4vm0vt.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <X+CgJCj7/tadldUg@danh.dev> ("Đoàn Trần Công Danh"'s message of "Mon, 21 Dec 2020 20:16:20 +0700")

Đoàn Trần Công Danh  <congdanhqx@gmail.com> writes:

> On 2020-12-20 01:23:05-0300, Érico Rolim <erico.erc@gmail.com> wrote:
>> Hi!
>> 
>> When using the command
>> 
>>   git log --patch --name-status
>> 
>> It seems the name-status flag somehow overrides the patch flag, by which I mean
>> that I get the same output as simply running
>> 
>>   git log --name-status
>> 
>> It would be nice for the combination of these two flags to work, as it would
>> allow one to view both a summary of changed files as well as the changes
>> themselves, at the same time.
>
> I'm not arguing if this your expectation is make sense or not,
> however, the Documentation says something about "Show only"...

Perhaps the documentation would need to be clarified?  I suspect
this is not very useful combination [*1*] and if this were years
ago, I would suggest making the command line error out, instead of
silently ignore one and keep the other one in effect.


[Footnote]

*1* "--patch --stat --summmary" was designed as the standard "both a
    summary as well as the changes".

  reply	other threads:[~2020-12-21 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20  4:23 [BUG] In git-log, --name-status flag overrides the --patch flag Érico Rolim
2020-12-21 13:16 ` Đoàn Trần Công Danh
2020-12-21 19:09   ` Junio C Hamano [this message]
2020-12-23 23:54     ` Đoàn Trần Công Danh

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=xmqq5z4vm0vt.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=congdanhqx@gmail.com \
    --cc=erico.erc@gmail.com \
    --cc=git@vger.kernel.org \
    /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).