From: Mircea Bardac <dev@mircea.bardac.net>
To: Ian Hilt <Ian.Hilt@gmx.com>
Cc: git@vger.kernel.org
Subject: Re: git blame for a commit
Date: Mon, 23 Jun 2008 10:04:16 +0100 [thread overview]
Message-ID: <485F6710.1080300@mircea.bardac.net> (raw)
In-Reply-To: <alpine.LFD.1.10.0806222300410.23258@sys-0.hiltweb.site>
Ian Hilt wrote:
> On Sun, 22 Jun 2008 at 11:32pm +0100, Mircea Bardac wrote:
>> 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.
>
> Sounds like you want to track files rather than content. Git tracks the
> latter.
Hmm... I'm not really sure that my initial intention was to track files.
I've given this some more thought and I realized that what I actually
want is a "git diff" with blame info included. I want this information
in order to facilitate code reviewing.
It is true that this would be a front-end functionality, but I am not
sure at the moment what the best approach would be for something like
this. I would see this something like
$ git diff --blame[="parameters_for_blame"] commit1..commit2
but this is just a thought.
Has anyone tried blaming a "git diff"?
Many thanks.
--
Mircea
http://mircea.bardac.net
next prev parent reply other threads:[~2008-06-23 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 22:32 git blame for a commit Mircea Bardac
2008-06-23 3:40 ` Ian Hilt
2008-06-23 9:04 ` Mircea Bardac [this message]
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=485F6710.1080300@mircea.bardac.net \
--to=dev@mircea.bardac.net \
--cc=Ian.Hilt@gmx.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;
as well as URLs for NNTP newsgroup(s).