author | Steffen Prohaska <prohaska@zib.de> | |
Sat, 6 Oct 2007 09:29:02 +0000 (11:29 +0200) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 10 Oct 2007 06:26:00 +0000 (02:26 -0400) | ||
commit | be700fe30fd17b3f9b600de9110c74035091a007 | |
tree | 6b9c630376eda0ec5ccfdb4537a69a1f7d6ccfa0 | tree | snapshot |
parent | 3ea16e569abce653e02632995aa32287d2f54360 | commit | diff |
git-gui: add directory git-gui is located in to PATH (on Windows)
This commit modifies PATH to include a good guess where git
could be found. The first location to search for executable is
the directory git-gui is installed in. This is a good guess for
a sane installation.
Even if git is not available in PATH, git-gui is now able
to find it. Hence git-gui can be passed to wish as an absolute
path without caring about the environment.
We must modify PATH to be able to spawn shell based git commands.
For builtins it would be sufficient to located them and execute
them with their absolute path. But for shell based git commmands
PATH needs to be modified.
Signed-off-by: Steffen Prohaska <prohaska@zib.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
This commit modifies PATH to include a good guess where git
could be found. The first location to search for executable is
the directory git-gui is installed in. This is a good guess for
a sane installation.
Even if git is not available in PATH, git-gui is now able
to find it. Hence git-gui can be passed to wish as an absolute
path without caring about the environment.
We must modify PATH to be able to spawn shell based git commands.
For builtins it would be sufficient to located them and execute
them with their absolute path. But for shell based git commmands
PATH needs to be modified.
Signed-off-by: Steffen Prohaska <prohaska@zib.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui.sh | diff | blob | history |