From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] git-gui: A commit / fetch / push interface
Date: Tue, 07 Nov 2006 09:58:18 +0100 [thread overview]
Message-ID: <eiphq0$pdf$1@sea.gmane.org> (raw)
In-Reply-To: 20061107083603.GB9622@spearce.org
Shawn Pearce wrote:
> Paul Mackerras originally started a thread about gitool, a graphical
> interface for creating commits:
>
> http://thread.gmane.org/gmane.comp.version-control.git/26415
[...]
> I have posted a repository with the source on pasky's service:
>
> http://repo.or.cz/w/git-gui.git
[...]
> Suggestions for improvement (or patches!) are most welcome.
> Better naming suggestions are also welcome. :)
I have added it to http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
By the way, do you know if (h)gct is actively developed against git?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-07 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 8:36 [RFC] git-gui: A commit / fetch / push interface Shawn Pearce
2006-11-07 8:58 ` Jakub Narebski [this message]
2006-11-07 22:46 ` Paul Mackerras
2006-11-08 5:46 ` Liu Yubao
2006-11-08 5:55 ` Shawn Pearce
2006-11-08 6:03 ` Shawn 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='eiphq0$pdf$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).