From: Chris Packham <judge.packham@gmail.com>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Documentation for git gui blame
Date: Tue, 12 Oct 2010 09:27:11 -0700 [thread overview]
Message-ID: <4CB48C5F.2030007@gmail.com> (raw)
In-Reply-To: <4CB48909.6050708@workspacewhiz.com>
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
next prev parent reply other threads:[~2010-10-12 16:27 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 [this message]
2010-10-12 19:50 ` Jakub Narebski
2010-10-12 21:46 ` Chris Packham
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=4CB48C5F.2030007@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).