From: demerphq <demerphq@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: git diff --summary only seems to work when combined with --stat
Date: Tue, 7 Dec 2010 07:55:01 +0100 [thread overview]
Message-ID: <AANLkTinOCR1UpgZJNyxQNUTgK1A603YhOoEy-y-0v8AP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinuQoJLfDq8HhUd=FLoqosVD23MU6ch6Ea2iVSJ@mail.gmail.com>
On 7 December 2010 07:53, demerphq <demerphq@gmail.com> wrote:
> On 6 December 2010 22:03, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Hi Yves,
>>
>> demerphq wrote:
>>
>>> It seems like the --summary option only works in combination --stat.
>>>
>>> It doesn't seem to work if I use it by itself, nor in combination with
>>> --name-status or --num-stat. And depending on the order, it either
>>> does nothing, or causes a usage note.
>>
>> It is tricky, but as you noticed --summary is not actually about the
>> diffstat. --summary affects the output summarizing new files and
>> renamed files.
>>
>> Example:
>>
>> $ git diff --summary v1.7.2..v1.7.3
>> delete mode 100644 Documentation/RelNotes-1.5.0.1.txt
>> delete mode 100644 Documentation/RelNotes-1.5.0.2.txt
>> [...]
>>
>>> $ git diff --name-status --sumary HEAD^
>>> usage: git diff <options> <rev>{0,2} -- <path>*
>>
>> There is an 'm' missing here. :)
>
> Thanks for your reply. It turns out that was a mis-paste. I tried both
> splelings of summary. ;-)
>
> And none of them produce output.
>
> $ git diff --summary HEAD^..HEAD
> $ git diff --summary HEAD^^..HEAD
> $ git diff --summary HEAD..HEAD^
> $ git diff --summary HEAD^
>
> So why does it work for you but not for me?
Ah. Not enough coffee. It "doesnt work" because I am not adding or
renaming a file here?
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
prev parent reply other threads:[~2010-12-07 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 20:55 git diff --summary only seems to work when combined with --stat demerphq
2010-12-06 21:03 ` Jonathan Nieder
2010-12-07 6:53 ` demerphq
2010-12-07 6:55 ` demerphq [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=AANLkTinOCR1UpgZJNyxQNUTgK1A603YhOoEy-y-0v8AP@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).