From: Pavel Roskin <proski@gnu.org>
To: Paul Mackerras <paulus@samba.org>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] gitk: Add "Refs" menu
Date: Tue, 11 Oct 2005 21:26:20 -0400 [thread overview]
Message-ID: <1129080380.2427.21.camel@dv> (raw)
In-Reply-To: <17227.44393.412591.267878@cargo.ozlabs.ibm.com>
Hi, Paul!
On Tue, 2005-10-11 at 22:17 +1000, Paul Mackerras wrote:
> Pavel Roskin writes:
>
> > This patch adds "Refs" menu to gitk. It makes all branches, tags and
> > other ref objects appear as menu items. Selecting one of the items
> > selects the corresponding line in the view.
>
> Sorry I haven't responded before - I have got way behind with my email
> due to a vacation and to concentrating on the merge of the ppc32 and
> ppc64 kernel sources. It will probably be a bit longer before I can
> get to look at this.
No problem. Thank you for letting me know.
I'm not a GUI designer and I'm not experienced in Tcl/Tk, so I'll
appreciate critical look at the patches.
I think that gitk should move away from being just a frontend to
git-rev-list. There is more information in the repository, such as
tags, branches, stgit patches etc. All this information needs to be
represented in some way, and using the menu was just the first approach.
Browsing trees and opening files for a given commit would be great and
helpful from developers migrating from CVS.
And making gitk cooperate with stgit would be a killer application not
just for gitk and stgit, but for git itself (i.e. it could be the reason
why git is chosen for development over e.g. Mercurial for new projects).
I don't want to distract you from PPC work, but your return to gitk
development would be very welcome :-)
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2005-10-12 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 0:38 [PATCH] gitk: Add "Refs" menu Pavel Roskin
2005-10-06 4:11 ` [PATCH] gitk: Add "Refs" menu - revised Pavel Roskin
2005-10-11 12:17 ` [PATCH] gitk: Add "Refs" menu Paul Mackerras
2005-10-12 1:26 ` Pavel Roskin [this message]
2005-10-12 7:31 ` Sven Verdoolaege
2005-10-12 14:34 ` Pavel Roskin
2005-10-12 11:55 ` Marco Costalba
2005-10-12 16:03 ` Pavel Roskin
2005-10-12 17:47 ` H. Peter Anvin
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=1129080380.2427.21.camel@dv \
--to=proski@gnu.org \
--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).