Felipe Contreras [off-list ref] writes:
On Wed, May 22, 2013 at 5:38 PM, Junio C Hamano [off-list ref] wrote:
...
quoted
As I already said in the above, the answer is no, when you are
trying to find who moved the code from the original place.
But I'm not trying to find who moved the code, I'm trying to find
related commits; hence the name 'git related'.
The person who moved the code will be on the list regardless,
That is exactly the point I have been trying to raise. Does the
person appear in the list when you run blame with -CCC? You ask for
the body of the function, and the -C mode of blame sees through the
block-of-line movement across file boundaries, and goes straight to
the last commit that touched the body of the function in its original
file, no?
On Wed, May 22, 2013 at 5:53 PM, Junio C Hamano [off-list ref] wrote:
Felipe Contreras [off-list ref] writes:
quoted
On Wed, May 22, 2013 at 5:38 PM, Junio C Hamano [off-list ref] wrote:
...
quoted
As I already said in the above, the answer is no, when you are
trying to find who moved the code from the original place.
But I'm not trying to find who moved the code, I'm trying to find
related commits; hence the name 'git related'.
The person who moved the code will be on the list regardless,
That is exactly the point I have been trying to raise. Does the
person appear in the list when you run blame with -CCC? You ask for
the body of the function, and the -C mode of blame sees through the
block-of-line movement across file boundaries, and goes straight to
the last commit that touched the body of the function in its original
file, no?
I'm not familiar how the different -C options work, but I'm testing
right now and I see the commit that moved a file with both -C and
-CCC, but strangely enough, not if it's the previous commit (with
both).
--
Felipe Contreras