All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Joshua Jensen <jjensen@workspacewhiz.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Documentation for git gui blame
Date: Tue, 12 Oct 2010 14:46:48 -0700	[thread overview]
Message-ID: <4CB4D748.9040907@gmail.com> (raw)
In-Reply-To: <m3iq176vh2.fsf@localhost.localdomain>

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).

  reply	other threads:[~2010-10-12 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 16:12 Documentation for git gui blame Joshua Jensen
2010-10-12 16:27 ` Chris Packham
2010-10-12 19:50   ` Jakub Narebski
2010-10-12 21:46     ` Chris Packham [this message]
2010-10-13  2:32     ` Joshua Jensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB4D748.9040907@gmail.com \
    --to=judge.packham@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jjensen@workspacewhiz.com \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.