git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar" <aneesh.kumar@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: git-gui blametool
Date: Mon, 12 Feb 2007 23:06:02 +0530	[thread overview]
Message-ID: <cc723f590702120936y64044ac4r86698b5d7e540bd8@mail.gmail.com> (raw)
In-Reply-To: <20070212173218.GD29621@spearce.org>

On 2/12/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> "Aneesh Kumar K.V" <aneesh.kumar@gmail.com> wrote:
> > I found the git-gui blame tool interface quiet confusing with the all
> > those color code. What does the color code actually mean ?
>
> Can you try the version of git-gui that Junio pushed out to `master`
> last night?
>
> > A simple
> > interface would be
> >
> > [ commit ] [ line number ] [ code ]
> >
> > ....
> > ...
> > --------------------------------------
> > commit details of the selected commit
>
> Because it uses this interface.  Almost.  It doesn't show the
> [commit] column.
>

I tried the same one. I was requesting to add the commit column. Right
now the interface is pretty confusing. After some reading of the code
i figured out that colours have a specific meaning. May be we need to
add a manual to the same.

but any how having commit in a column like this is really nice. I just
sent a new patch for blameview. That should give an idea how much the
interface looks better.

-aneesh

  reply	other threads:[~2007-02-12 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 14:32 git-gui blametool Aneesh Kumar K.V
2007-02-12 16:28 ` Aneesh Kumar K.V
2007-02-12 17:54   ` Jeff King
2007-02-12 16:33 ` Aneesh Kumar K.V
2007-02-12 17:32 ` Shawn O. Pearce
2007-02-12 17:36   ` Aneesh Kumar [this message]
2007-02-12 19:20     ` Shawn O. Pearce

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=cc723f590702120936y64044ac4r86698b5d7e540bd8@mail.gmail.com \
    --to=aneesh.kumar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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).