Re: git blame for a commit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux