From: John Keeping <john@keeping.me.uk>
To: Olaf Hering <olaf@aepfle.de>
Cc: git@vger.kernel.org
Subject: Re: git log fails to show all changes for a file
Date: Tue, 14 Jul 2015 08:45:08 +0100 [thread overview]
Message-ID: <20150714074508.GE1451@serenity.lan> (raw)
In-Reply-To: <20150714073035.GA22707@aepfle.de>
On Tue, Jul 14, 2015 at 09:30:35AM +0200, Olaf Hering wrote:
>
> I wonder why this command fails to show all commits that modify a given
> function:
>
> linux.git $ git log -p -M --stat -- drivers/hv/channel_mgmt.c
>
> With commit 1f656ff3fdddc2f59649cc84b633b799908f1f7b init_vp_index() has
> "const uuid_le *type_guid" already. And somewhere between commit
> d3ba720dd58cdf6630fee4b89482c465d5ad0d0f and the one above the "const"
> was added. But git log does not show this commit.
>
> Why is that so, and whats the command to really show all and every change?
It was added in an evil merge (f9da455b93f6ba076935b4ef4589f61e529ae046),
try:
git log -p -M --stat --cc -- drivers/hv/channel_mgmt.c
next prev parent reply other threads:[~2015-07-14 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 7:30 git log fails to show all changes for a file Olaf Hering
2015-07-14 7:45 ` John Keeping [this message]
2015-07-14 7:59 ` Olaf Hering
2015-07-14 17:54 ` Andreas Schwab
2015-07-14 19:16 ` Linus Torvalds
2015-07-15 16:29 ` Junio C Hamano
2015-07-15 17:13 ` Linus Torvalds
2015-07-15 17:58 ` Junio C Hamano
2015-07-15 18:11 ` Linus Torvalds
2015-07-15 18:17 ` Junio C Hamano
2015-07-15 18:57 ` Jeff King
2015-07-15 19:22 ` Junio C Hamano
2015-07-15 19:17 ` Linus Torvalds
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150714074508.GE1451@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=olaf@aepfle.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).