From: "Eric Raible" <raible@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Cc: paulus@samba.org
Subject: RFH: gitk equivalent of "git log -p --full-diff file.cpp"
Date: Mon, 6 Oct 2008 19:04:14 -0700 [thread overview]
Message-ID: <279b37b20810061904n4f50f650l81590cb6fd239282@mail.gmail.com> (raw)
Hello All -
Hopefully I'm just being dense, but there's a useful tortoisesvn feature that
(so far) I haven't found in gitk. Blasphemy! Sniveling windoze luser, etc^2.
Anyway what I'm looking for is the gitk equivalent of:
git log -p --full-diff file.cpp
That is to say: I want to see all commits which touch a given
file along with all of the other files changed by that commit.
gitk -p --full-diff EntryPoints.cpp
doesn't quite do it - it treats the "extra" diffs as part of the commit msg.
Anyone got more if a clue than me?
Thanks - Eric
PS - Aside from aliases, am I missing a simpler spelling of the above
git log command?
next reply other threads:[~2008-10-07 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 2:04 Eric Raible [this message]
2008-10-07 2:27 ` RFH: gitk equivalent of "git log -p --full-diff file.cpp" Jeff King
2008-10-07 3:45 ` Eric Raible
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=279b37b20810061904n4f50f650l81590cb6fd239282@mail.gmail.com \
--to=raible@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).