Documentation for git gui blame

Documentation for git gui blame

[Joshua Jensen]

  Is there any documentation for git gui blame that explains what the 
two left columns containing 4 letter SHAs are?

What does "Blame Parent Commit" mean?

Thanks!

Josh

Re: Documentation for git gui blame

[Chris Packham]

On 12/10/10 09:12, Joshua Jensen wrote:
>  Is there any documentation for git gui blame 

Not sure but it's displaying the same info as git blame so start with
man git-blame. That probably covers most of what you want to know

> that explains what the two left columns containing 4 letter SHAs are?

These are the first 4 characters of the commit id that last
added/changed that line of code. Basically the standard abbreviated 8
character SHA1 would take up too much screen real estate. You can still
use a 4 character SHA as long as there aren't any commits in your tree
that start with the same 4 characters (the possibility of collisions
exists with 8 character ones too, it's just less likely).

> 
> What does "Blame Parent Commit" mean?
> 

It means that you have decided that the commit that it currently has
selected is not interesting and you want to see the previous commit that
modified that section (e.g. it was just some formatting change and you
want the commit that actually added the code in question).

> Thanks!
> 
> Josh
> -- 
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Documentation for git gui blame

[Jakub Narebski]

Chris Packham <judge.packham@gmail.com> writes:

> On 12/10/10 09:12, Joshua Jensen wrote:
> >  Is there any documentation for git gui blame 
> 
> Not sure but it's displaying the same info as git blame so start with
> man git-blame. That probably covers most of what you want to know
> 
> > that explains what the two left columns containing 4 letter SHAs are?
> 
> These are the first 4 characters of the commit id that last
> added/changed that line of code.

Note that there are *two* columns because one column contains plain blame,
and second contains blame with code movement and copying detection and
discarding changes in whitespace (like "git blame -C -C -w").  So if those
columns are different, one column would show commit that put code here,
and the other would show commit that changed this code.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

Re: Documentation for git gui blame

[Chris Packham]

On 12/10/10 12:50, Jakub Narebski wrote:
> Chris Packham <judge.packham@gmail.com> writes:
> 
>> On 12/10/10 09:12, Joshua Jensen wrote:
>>>  Is there any documentation for git gui blame 
>>
>> Not sure but it's displaying the same info as git blame so start with
>> man git-blame. That probably covers most of what you want to know
>>
>>> that explains what the two left columns containing 4 letter SHAs are?
>>
>> These are the first 4 characters of the commit id that last
>> added/changed that line of code.
> 
> Note that there are *two* columns because one column contains plain blame,
> and second contains blame with code movement and copying detection and
> discarding changes in whitespace (like "git blame -C -C -w").  So if those
> columns are different, one column would show commit that put code here,
> and the other would show commit that changed this code.

Sorry, my bad I should have actually taken a look before responding (and
read the question properly).

Re: Documentation for git gui blame

[Joshua Jensen]

  ----- Original Message -----
From: Jakub Narebski
Date: 10/12/2010 1:50 PM
> Chris Packham<judge.packham@gmail.com>  writes:
>
>> On 12/10/10 09:12, Joshua Jensen wrote:
>>>   Is there any documentation for git gui blame that explains what the two left columns containing 4 letter SHAs are?
>> These are the first 4 characters of the commit id that last
>> added/changed that line of code.
> Note that there are *two* columns because one column contains plain blame,
> and second contains blame with code movement and copying detection and
> discarding changes in whitespace (like "git blame -C -C -w").  So if those
> columns are different, one column would show commit that put code here,
> and the other would show commit that changed this code.
Ah, great!  That's what the other column is all about!

Thanks, Chris, for the Blame Parent Commit info, too.

Josh