git blame: two "-C"s versus just a single -C

Sitaram Chamarty· Jan 23, 2009, 11:28 UTC · lore

I seem to recall (and the docs indicate) that when you *copy* (not move, just copy) a function from file1.c to file2.c, commit, and then do a "git blame -C -C file2.c", it should tell you that those lines came from file1.c

Is this not true? Git 1.6.1, I tried this on a dummy branch where I just copied a good sized function (about 45 lines) from one C program and dumped it at the bottom of a second one, and neither the gui blame nor the CLI blame show me that the lines came from elsewhere.

What am I doing wrong?

Sitaram Chamarty· Jan 23, 2009, 19:12 UTC · re: Sitaram Chamarty · lore

Re: git blame: two "-C"s versus just a single -C

On 2009-01-23, Sitaram Chamarty <sitaramc@gmail.com> wrote:

Show 12 quoted lines

> I seem to recall (and the docs indicate) that when you
> *copy* (not move, just copy) a function from file1.c to
> file2.c, commit, and then do a "git blame -C -C file2.c", it
> should tell you that those lines came from file1.c
>
> Is this not true?  Git 1.6.1, I tried this on a dummy branch
> where I just copied a good sized function (about 45 lines)
> from one C program and dumped it at the bottom of a second
> one, and neither the gui blame nor the CLI blame show me
> that the lines came from elsewhere.
>
> What am I doing wrong?

(replying to myself...)

It works when I give it three "-C" arguments. I thought it was supposed to be 2 though.