From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: "git diff --summary --diff-filter=AD" without --stat does not work.
Date: Tue, 03 Oct 2006 13:36:41 -0700 [thread overview]
Message-ID: <7vejtpm90m.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0610032221330.14200@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Tue, 3 Oct 2006 22:23:02 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> I think it should only show create/delete notes and not even
>> diff text.
>
> What exactly is the problem? My tree only has minor patches, which should
> not affect the output of your command, and it does this:
>
> $ git diff --summary --diff-filter=AD next..pu
> create mode 100644 builtin-diff-status.c
> create mode 100644 para-walk.c
> create mode 100644 para-walk.h
> create mode 100644 test-para.c
I suspect the real issue is that it does not turn 'recursive'
on.
prev parent reply other threads:[~2006-10-03 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 19:15 "git diff --summary --diff-filter=AD" without --stat does not work Junio Hamano
2006-10-03 20:23 ` Johannes Schindelin
2006-10-03 20:36 ` 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=7vejtpm90m.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox