From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: merges and git log --stat
Date: Thu, 6 May 2010 22:36:39 +0200 [thread overview]
Message-ID: <20100506203639.GV4599@neumann> (raw)
In-Reply-To: <7vsk64hjq4.fsf@alter.siamese.dyndns.org>
That was fast, thank you.
On Thu, May 06, 2010 at 01:13:23PM -0700, Junio C Hamano wrote:
> SZEDER Gábor <szeder@ira.uka.de> writes:
>
> > I've just noticed that 'git log --stat' does not print the diffstat
> > for merge commits. Is this intentional?
>
> It's very much designed so. You cannot clearly define "diff from which
> parent you would want to see".
I see. Perhaps it would make sense to show the diffstat from the
point of view of the first parent, but maybe I'm biased by my current
use case. Anyway, it seems that I can easily get what I need with a
bit of scripting, so it's not a major issue.
Best,
Gábor
next prev parent reply other threads:[~2010-05-06 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 19:26 merges and git log --stat SZEDER Gábor
2010-05-06 20:13 ` Junio C Hamano
2010-05-06 20:36 ` SZEDER Gábor [this message]
2010-05-06 23:58 ` Junio C Hamano
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=20100506203639.GV4599@neumann \
--to=szeder@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).