| commit | 6e4ba05c7fee0d0140e2057b63f5ca4eea9a6053 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 2 Sep 2007 19:19:07 +0000 (2 15:19 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 4 Sep 2007 03:01:44 +0000 (3 23:01 -0400) | ||
| tree | 01a9096e0bb99779e8987bfeff055b8df7effe80 | treesnapshot (tar.gz zip) |
| parent | c80d25dbce759a8483ffc1f085fdf4cd63cf9f05 | commitdiff |
git-gui: Correct starting of git-remote to handle -w option
Current versions of git-remote apparently are passing the -w option
to Perl as part of the shbang line:
#!/usr/bin/perl -w
this caused a problem in git-gui and gave the user a Tcl error with
the message: "git-remote not supported: #!/usr/bin/perl -w".
The fix for this is to treat the shbang line as a Tcl list and look
at the first element only for guessing the executable name. Once
we know the executable name we use the remaining elements (if any
exist) as arguments to the executable, before the script filename.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Current versions of git-remote apparently are passing the -w option
to Perl as part of the shbang line:
#!/usr/bin/perl -w
this caused a problem in git-gui and gave the user a Tcl error with
the message: "git-remote not supported: #!/usr/bin/perl -w".
The fix for this is to treat the shbang line as a Tcl list and look
at the first element only for guessing the executable name. Once
we know the executable name we use the remaining elements (if any
exist) as arguments to the executable, before the script filename.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui.sh | diffblobblamehistory |