From: Jeff King <peff@peff.net>
To: Marco Costalba <mcostalba@gmail.com>
Cc: davvid@gmail.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH ugit] Allow user to choose history browser tool
Date: Thu, 3 Jan 2008 17:39:21 -0500 [thread overview]
Message-ID: <20080103223920.GA17530@coredump.intra.peff.net> (raw)
In-Reply-To: <e5bfff550801030408w1512e458x136f6be0371c13c2@mail.gmail.com>
On Thu, Jan 03, 2008 at 01:08:17PM +0100, Marco Costalba wrote:
> Instead of hard linking gitk let the user set
> the preferred history visualization tool in settings dialog.
This is the exact situation that the 'git view' builtin alias was
designed for. If every porcelain which spawned a viewer used 'git view',
then the user would only need to configure one place (but note that 'git
view' has never even made it out of next, so I am not recommending it
instead of your patch, but just making a note).
-Peff
prev parent reply other threads:[~2008-01-03 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 12:08 [PATCH ugit] Allow user to choose history browser tool Marco Costalba
2008-01-03 12:35 ` David
2008-01-03 22:39 ` Jeff King [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=20080103223920.GA17530@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
/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).