From: Junio C Hamano <gitster@pobox.com>
To: "Janusz Białobrzewski" <Janusz.Bialobrzewski@biu.pl>
Cc: git@vger.kernel.org
Subject: Re: Combined diff with name-only option
Date: Fri, 10 Jul 2015 10:47:46 -0700 [thread overview]
Message-ID: <xmqq7fq7lxa5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <559FA0EF.2000409@biu.pl> ("Janusz Białobrzewski"'s message of "Fri, 10 Jul 2015 12:39:43 +0200")
Janusz Białobrzewski <Janusz.Bialobrzewski@biu.pl> writes:
> Is it a bug or is it done by design?
I suspect the answer is "no and not really". The truth would be
closer to: we didn't bother to write code in the command line parser
to check and flag it as an error when "--cc" and "--name-only" is
given together.
Unlike "-c" that works solely on the tree level changes, "--cc"
looks into blob contents involved in the merge, but things like
"--name-status", etc., do not work at blob levels (you can consider
that part is "by design").
Similarly, if you make a whitespace-only change to a file and use
git diff-tree -b -p
you will still see the name of the commit object, but no patch.
git diff-tree -b --name-only
still reports the modified paths as tree-level differences.
prev parent reply other threads:[~2015-07-10 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 10:39 Combined diff with name-only option Janusz Białobrzewski
2015-07-10 17:47 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7fq7lxa5.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Janusz.Bialobrzewski@biu.pl \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.