From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: gitk-1.0 released
Date: Thu, 19 May 2005 15:24:11 +0200 [thread overview]
Message-ID: <20050519132411.GA29111@elte.hu> (raw)
In-Reply-To: <17036.36624.911071.810357@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> I have released a new version of gitk. I got brave and called it 1.0
> and it is at:
>
> http://ozlabs.org/~paulus/gitk-1.0
very nice! Works well and it's pretty fast on a 2GHz P4.
a bugreport: when looking at the main git history, the following commit
seems to be rendered incorrectly:
211232bae64bcc60bbf5d1b5e5b2344c22ed767e
The "Octopus merge ..." text is incorrectly overlayed with a graph line.
here's a feature wishlist if you dont mind:
- the ability to copy & paste from all the windows would be nice. (e.g.
in the bugreport above i had to type down the "Octopus merge .." text
instead of pasting it from gitk)
- i guess this one is on your todo list: the history graph of a single
object (file).
- first window appearance on an uncached repository can be pretty slow
due to disk seeks - so it might make sense to display something (an
hourglass?) sooner - when i first started it i thought it hung. On
already cached repositories the window comes up immediately, and the
list of commits is updated dynamically.
(and the biggest missing feature of GIT right now is author +
last-commit annotated file viewing which could be integrated into gitk
a'ka BK's revtool: selecting a given line of the file would bring one to
that commit, etc.)
Ingo
next prev parent reply other threads:[~2005-05-19 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 13:05 gitk-1.0 released Paul Mackerras
2005-05-19 13:24 ` Ingo Molnar [this message]
2005-05-19 13:30 ` Ingo Molnar
2005-05-19 22:32 ` Paul Mackerras
2005-05-20 11:22 ` Ingo Molnar
2005-05-20 11:33 ` Ingo Molnar
2005-05-20 18:18 ` Kari Hameenaho
2005-05-20 19:07 ` Linus Torvalds
2005-05-21 6:40 ` Jon Seymour
2005-05-21 16:35 ` Linus Torvalds
2005-05-19 23:13 ` Benjamin Herrenschmidt
2005-05-20 4:55 ` Frank Sorenson
2005-05-20 1:10 ` walt
2005-05-28 11:47 ` Ingo Molnar
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=20050519132411.GA29111@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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).