Re: [RFC PATCH 2/2] Teach git-blame --gui how to start git-gui blame

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jun 22, 2007, 03:56 UTC
Message-ID: <20070622035652.GD17393@spearce.org>
In-Reply-To: <7vtzt13k4o.fsf@assigned-by-dhcp.pobox.com>

Junio C Hamano <gitster@pobox.com> wrote:

> Hmm.  Now, how does "git-blame" tell if there is usable git-gui
> installed with it?  Will we have "git-gui --list-features"?

It can run `git gui version` and check to see that it is >= 0.7.3.
 
;-)

I'm actually not sure we want to apply this patch, hence the RFC prefix I put on it. Jakub suggested it, this crude implementation was easy enough to hack together, so I posted a patch for someone to play with if they were so inclined.

Maybe we should just put a link in the git-blame manual page to the git-gui manual page:

diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 66f1203..599e10b 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -36,6 +36,9 @@ $ git log --pretty=oneline -S'blame_usage'
 ea4c7f9bf69e781dd0cd88d2bccb2bf5cc15c9a7 git-blame: Make the output
 -----------------------------------------------------------------------------
 
+A powerful graphical viewer for the output of git-blame can be
+accessed through the blame subcommand of gitlink:git-gui[1].
+
 OPTIONS
 -------
 include::blame-options.txt[]
@@ -184,7 +187,8 @@ commit commentary), a blame viewer won't ever care.
 
 SEE ALSO
 --------
-gitlink:git-annotate[1]
+gitlink:git-annotate[1],
+gitlink:git-gui[1]
 
 AUTHOR
 ------

-- 
Shawn.