From: "Shawn O. Pearce" <spearce@spearce.org>
To: Alexander Gavrilov <angavrilov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH (GIT-GUI) v2 0/5] Add a customizable Tools menu.
Date: Sun, 16 Nov 2008 13:56:15 -0800 [thread overview]
Message-ID: <20081116215615.GE2932@spearce.org> (raw)
In-Reply-To: <1226861211-16995-1-git-send-email-angavrilov@gmail.com>
Alexander Gavrilov <angavrilov@gmail.com> wrote:
> This series adds a customizable Tools menu, that can
> be used to call any external commands from Git Gui.
> It reduces the inconvenience of using tools like git-svn
> with GUI, by removing the need to jump between the
> terminal and the GUI even for simple actions. QGit
> already has a similar feature.
Thanks. This is really slick. Its in my tree now.
Given that 1.6.1 is entering rc mode, I'm probably not going to be
accepting any more new features into my master branch until 1.6.1
freezes. Everything after this will wind up in `pu` until I cut
git-gui 0.12.0.
--
Shawn.
prev parent reply other threads:[~2008-11-16 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 18:46 [PATCH (GIT-GUI) v2 0/5] Add a customizable Tools menu Alexander Gavrilov
2008-11-16 18:46 ` [PATCH (GIT-GUI) v2 1/5] git-gui: Implement system-wide configuration handling Alexander Gavrilov
2008-11-16 18:46 ` [PATCH (GIT-GUI) v2 2/5] git-gui: Fix the after callback execution in rescan Alexander Gavrilov
2008-11-16 18:46 ` [PATCH (GIT-GUI) v2 3/5] git-gui: Add a Tools menu for arbitrary commands Alexander Gavrilov
2008-11-16 18:46 ` [PATCH (GIT-GUI) v2 4/5] git-gui: Allow Tools request arguments from the user Alexander Gavrilov
2008-11-16 18:46 ` [PATCH (GIT-GUI) v2 5/5] git-gui: Implement automatic rescan after Tool execution Alexander Gavrilov
2008-11-16 21:56 ` Shawn O. Pearce [this message]
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=20081116215615.GE2932@spearce.org \
--to=spearce@spearce.org \
--cc=angavrilov@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).