On 09/08/2014 07:19 AM, Jeff King wrote:
Have you tried "git log -L 2235,2235:fs/ext4/mballoc.c --
fs/ext4/mballoc.c"? Can you compare your approach to that of "log -L"?
-Peff
Nice, but it doesn't seem to work 100 % (?)
tb@linux:~/projects/git/git.pu/t$ git log t3910-mac-os-precompose.sh |
On Sun, Sep 07, 2014 at 06:05:13PM -0500, xmeng wrote:
> The problem with git-blame is that it only reports the last author/commit
> that changed the line, regardless of the magnitude of the change. Sometimes,
> the last author may only change a tiny part of the code and should not be
> blamed. I
Hi all,
I have been using git-blame to track who changed a line of code or who
to blame for a line of code. It is easy to use. For example, for this
particular line of code:
$ git blame -L 2235,2235 fs/ext4/mballoc.c
85556c9a (Wei Yongjun 2012-09-26 20:43:37 -0400 2235)
meta_group_info[i]
3 matches
Mail list logo
