From: Junio C Hamano <gitster@pobox.com>
To: Karthik R <karthikr@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: [PATCH][resend] git-svn: Respect GIT_SSH setting
Date: Mon, 17 Aug 2009 16:21:54 -0700 [thread overview]
Message-ID: <7vzl9ykovh.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4A89E185.2010307@fastmail.fm> (Karthik R.'s message of "Mon\, 17 Aug 2009 18\:02\:29 -0500")
Karthik R <karthikr@fastmail.fm> writes:
> +# If GIT_SSH is set, also set SVN_SSH...
> +$ENV{SVN_SSH} = $ENV{GIT_SSH} if defined $ENV{GIT_SSH};
> +# ... and escape \s in shell-variable on Windows
> +if ($^O eq 'MSWin32' || $^O eq 'msys') {
> + $ENV{SVN_SSH} =~ s/\\/\\\\/g if defined $ENV{SVN_SSH};
> +}
> +
Two questions.
- What if a user has SVN_SSH exported _and_ wants to use a different one
from the one s/he uses for git? Naturally such a user would set both
environment variables and differently, but this seems to override the
value in SVN_SSH;
- Can a user have SVN_SSH exported, on MSWin32 or msys, and use svn
outside git? If so, what does the value of SVN_SSH look like? Does it
typically have necessary doubling of backslashes already?
What I am getting at is, if the patch should look something like this
instead:
if (! exists $ENV{SVN_SSH}) {
if (exists $ENV{GIT_SSH}) {
$ENV{SVN_SSH} = $ENV{GIT_SSH};
if ($^O eq 'MSWin32' || $^O eq 'msys') {
$ENV{SVN_SSH} =~ s/\\/\\\\/g;
}
}
}
next prev parent reply other threads:[~2009-08-17 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 23:02 [PATCH][resend] git-svn: Respect GIT_SSH setting Karthik R
2009-08-17 23:20 ` Johannes Schindelin
2009-08-18 4:33 ` Karthik R
2009-08-18 9:52 ` Johannes Schindelin
2009-08-17 23:21 ` Junio C Hamano [this message]
2009-08-17 23:47 ` Karthik R
2009-08-18 5:48 ` Karthik R
2009-08-18 19:25 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vzl9ykovh.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthikr@fastmail.fm \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox