aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2007-07-09 02:13:00 -0400
committerShawn O. Pearce <spearce@spearce.org>2007-07-09 02:13:00 -0400
commitc67298902ca36579b4cc43c1868cdb41279ef21b (patch)
treec7286b1466a57f7024eb947f92c68eac34c02377
parent02efd48f520d14012fc82c999172306a94862dee (diff)
downloadgit-c67298902ca36579b4cc43c1868cdb41279ef21b.tar.gz
git-c67298902ca36579b4cc43c1868cdb41279ef21b.tar.xz
git-gui: Assume unfound commands are known by git wrapper
If we cannot locate a command in $gitexecdir on our own then it may just be because we are supposed to run it by `git $name` rather than by `git-$name`. Many commands are now builtins, more are likely to go in that direction, and we may see the hardlinks in $gitexecdir go away in future versions of git. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
-rwxr-xr-xgit-gui.sh5
1 files changed, 4 insertions, 1 deletions
diff --git a/git-gui.sh b/git-gui.sh
index 53cf89876..9b342f084 100755
--- a/git-gui.sh
+++ b/git-gui.sh
@@ -315,7 +315,10 @@ proc _git_cmd {name} {
#
set v [list $::_sh [gitexec git-$name]]
} else {
- error "No [gitexec git-$name]"
+ # Assume it is builtin to git somehow and we
+ # aren't actually able to see a file for it.
+ #
+ set v [list $::_git $name]
}
set _git_cmd_path($name) $v
}