| commit | 6ecb26836b8fe1f3eefe306b79f3652b125d9be9 | |
| author | Sebastian Schuberth <sschuberth@gmail.com> | |
| Wed, 5 Oct 2011 09:14:38 +0000 (5 11:14 +0200) | ||
| committer | Sebastian Schuberth <sschuberth@gmail.com> | |
| Tue, 11 Oct 2011 21:13:30 +0000 (11 23:13 +0200) | ||
| tree | 07766e63963552c75275a85a2d2ef24c05be58c3 | treesnapshot (tar.gz zip) |
| parent | f0e86b3b664bbfdc7e8fabdb01518347f7e0d2f8 | commitdiff |
git-svn: On MSYS, escape and quote SVN_SSH also if set by the user
While GIT_SSH does not require any escaping / quoting (e.g. for paths
containing spaces), SVN_SSH requires it due to its use in a Perl script.
Previously, SVN_SSH has only been escaped and quoted automatically if it
was unset and thus derived from GIT_SSH. For user convenience, do the
escaping and quoting also for a SVN_SSH set by the user. This way, the
user is able to use the same unescaped and unquoted syntax for GIT_SSH
and SVN_SSH.
Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
While GIT_SSH does not require any escaping / quoting (e.g. for paths
containing spaces), SVN_SSH requires it due to its use in a Perl script.
Previously, SVN_SSH has only been escaped and quoted automatically if it
was unset and thus derived from GIT_SSH. For user convenience, do the
escaping and quoting also for a SVN_SSH set by the user. This way, the
user is able to use the same unescaped and unquoted syntax for GIT_SSH
and SVN_SSH.
Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
| git-svn.perl | diffblobblamehistory |