| commit | 454efb47b6199f70ec7992ea4bf459f193a43bb7 | |
| author | Markus Heidelberg <markus.heidelberg@web.de> | |
| Tue, 31 Mar 2009 23:55:36 +0000 (1 01:55 +0200) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 5 Apr 2009 20:05:29 +0000 (5 13:05 -0700) | ||
| tree | da4224407b2368f74156c64842e81ab409cbddde | treesnapshot (tar.gz zip) |
| parent | c9498339a40566c736a85238c29fd45d63510abe | commitdiff |
git-gui (Win): make "Explore Working Copy" more robust
Starting the Explorer from the git-gui menu "Explore Working Copy"
didn't work, when git-gui was started via Windows Explorer shell
extension (Git GUI Here) from a directory within the project.
The Explorer raised an error message like this:
Path "C:/somedir/worktree" is not available or not a directory
It worked when started from the project directory itself, because then
the path argument for the Explorer was just '.' (current directory)
without any problematic forward slashes.
To make it work, convert the path given as argument to explorer.exe to
its native format with backslashes.
Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Starting the Explorer from the git-gui menu "Explore Working Copy"
didn't work, when git-gui was started via Windows Explorer shell
extension (Git GUI Here) from a directory within the project.
The Explorer raised an error message like this:
Path "C:/somedir/worktree" is not available or not a directory
It worked when started from the project directory itself, because then
the path argument for the Explorer was just '.' (current directory)
without any problematic forward slashes.
To make it work, convert the path given as argument to explorer.exe to
its native format with backslashes.
Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui.sh | diffblobblamehistory |