public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail•com>
To: Ingo Molnar <mingo@elte•hu>
Cc: git@vger•kernel.org
Subject: Re: [ANNOUNCE] gitkdiff 0.1
Date: Thu, 28 Apr 2005 20:01:11 +0900	[thread overview]
Message-ID: <4270C277.4000303@gmail.com> (raw)
In-Reply-To: <20050428103655.GA14076@elte.hu>

Ingo Molnar wrote:
> * Tejun Heo <htejun@gmail•com> wrote:
> 
> 
>> Hello, guys.
>>
>> I've hacked tkdiff and made a commit viewing utility.  Just download
>>the following tarball and unpack it whereever PATH points to.  It
>>assumes that all base git executables are visible via PATH.
>>
>> http://home-tj.org/gitui/files/gitui-200504281405.tar.gz
> 
> 
> very nice!
> 
> there's only one other utility i'm missing: a tool that does the 
> equivalent of 'bk annotate' - and to possibly integrate it with gitkdiff 
> and git-viz. That would make 'history browsing' very powerful: to 
> flexibly switch between changeset history graph view, annotated file 
> view and changeset history within one utility.
> 
> 	Ingo

  Actually, I am thinking about making a full gui history thing.  With 
commit history graph, annoatated file history and all those stuff (I 
think it will look a lot like bk revtool).  Can't say how long it will 
take but maybe in a week.  So, if you have some ideas/suggestions, 
please let me know.

-- 
tejun

  reply	other threads:[~2005-04-28 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  5:14 [ANNOUNCE] gitkdiff 0.1 Tejun Heo
2005-04-28  5:49 ` Greg KH
2005-04-28 10:36 ` Ingo Molnar
2005-04-28 11:01   ` Tejun Heo [this message]
2005-12-09 10:45 ` Horst Kronstorfer
2005-12-09 12:56   ` Sven Verdoolaege
2005-12-09 14:55     ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2005-12-14 12:03 KRONSTORFER Horst
2005-12-19  4:28 ` Tejun Heo

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=4270C277.4000303@gmail.com \
    --to=htejun@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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