From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git log and merge commits
Date: Mon, 14 May 2007 18:56:11 +0200 [thread overview]
Message-ID: <f2a42g$ein$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.62.0705141803590.11269@pademelon.sonytel.be
[Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
git@vger.kernel.org]
Geert Uytterhoeven wrote:
> I noticed `git log -p' doesn't show the changes introduced by merge commits.
> This is true for plain `git log -p' and for `git log -p <filename>'.
Have you tried `git log -p --cc'?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-05-14 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 16:13 git log and merge commits Geert Uytterhoeven
2007-05-14 16:56 ` Jakub Narebski [this message]
2007-05-14 17:51 ` Linus Torvalds
2007-05-14 18:01 ` Geert Uytterhoeven
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='f2a42g$ein$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--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