From: Mircea Bardac <dev@mircea.bardac.net>
To: git@vger.kernel.org
Subject: git blame for a commit
Date: Sun, 22 Jun 2008 23:32:05 +0100 [thread overview]
Message-ID: <485ED2E5.3070906@mircea.bardac.net> (raw)
Hi everyone,
Is there any straightforward way of doing git blame for all the files
that got changed in a commit. Problems are renames, deletes and copies.
I was also thinking of git diff with a huge number of context lines, but
this one feels a bit hacking. "git diff" is also missing author info, so
"git blame" is a bit more desirable.
Has anyone ever done this before?
Many thanks.
--
Mircea
http://mircea.bardac.net
next reply other threads:[~2008-06-22 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 22:32 Mircea Bardac [this message]
2008-06-23 3:40 ` git blame for a commit Ian Hilt
2008-06-23 9:04 ` Mircea Bardac
2008-06-23 10:01 ` Jakub Narebski
2008-06-23 15:55 ` Ian Hilt
2008-06-23 16:29 ` Jakub Narebski
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=485ED2E5.3070906@mircea.bardac.net \
--to=dev@mircea.bardac.net \
--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;
as well as URLs for NNTP newsgroup(s).