summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 02efd48)
raw | patch | inline | side by side (parent: 02efd48)
author | Shawn O. Pearce <spearce@spearce.org> | |
Mon, 9 Jul 2007 06:13:00 +0000 (02:13 -0400) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Mon, 9 Jul 2007 06:13:00 +0000 (02:13 -0400) |
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>
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>
git-gui.sh | patch | blob | history |
diff --git a/git-gui.sh b/git-gui.sh
index 53cf89876fe9978500c911683e6245f92082ff30..9b342f08464c39d7096c987f3444772770962370 100755 (executable)
--- a/git-gui.sh
+++ b/git-gui.sh
#
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
}