From: Jakub Narebski <jnareb@gmail.com>
To: Marcus Comstedt <marcus@mc.pp.se>
Cc: git@vger.kernel.org
Subject: Re: git log --stat FILE
Date: Sun, 08 Aug 2010 04:54:48 -0700 (PDT) [thread overview]
Message-ID: <m339up48vz.fsf@localhost.localdomain> (raw)
In-Reply-To: <yf9wrs1fili.fsf@chiyo.mc.pp.se>
Marcus Comstedt <marcus@mc.pp.se> writes:
> Hi guys.
>
> I'm probably just missing something here, but I've run across a rather
> annoying behavior of log.
>
> When I do "git log --stat FILE", then only commits which touch FILE
> are displayed, as expected. However, contrary to expectation (well,
> my expectation at least), the stat shows that only one file (FILE) is
> modified by the commits, even if they actually modified multiple files.
> That's not what I wanted; I used FILE to select commits, not to
> control how they are presented. In fact, the information which is
> hidden is exactly that which I wanted to see; the whole reason for the
> --stat was that I wanted to know what _other_ files were modified
> together with FILE.
>
> What's worse, I could not find how to circumvent this behavior, [...]
See --full-diff option to git-log.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-08-08 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 11:29 git log --stat FILE Marcus Comstedt
2010-08-08 11:54 ` Jakub Narebski [this message]
2010-08-08 11:54 ` Lars Hjemli
2010-08-08 12:04 ` Marcus Comstedt
2010-08-08 12:26 ` Jakub Narebski
2010-08-08 12:35 ` Marcus Comstedt
2010-08-08 13:08 ` Jakub Narebski
2010-08-08 13:33 ` Marcus Comstedt
2010-08-08 15:31 ` [PATCH] Documentation/git-log: Clarify --full-diff Michael J Gruber
2010-08-09 7:45 ` Matthieu Moy
2010-08-09 19:57 ` 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=m339up48vz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=marcus@mc.pp.se \
/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.