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: Tue, 18 Aug 2009 12:25:09 -0700 [thread overview]
Message-ID: <7vk510diwa.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4A89EC07.2010402@fastmail.fm> (Karthik R.'s message of "Mon\, 17 Aug 2009 18\:47\:19 -0500")
Karthik R <karthikr@fastmail.fm> writes:
>> 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;
>>
> Do you mean user wants to use a different one with "git svn
> ... svn+ssh://" (than the one with "git clone ssh://") ?
Yes.
> In this case
> - defining SVN_SSH, but not GIT_SSH will still work (with this patch,
> GIT_SSH overrides)
Which means if you need to use GIT_SSH to specify one and SVN_SSH to
specify another, you have trouble. IOW, you cannot use anything but
whatever the default is for native git access over ssh:// protocol.
> - but SVN_SSH needs to have \\s.
>
> So unless the user already knew of this quirk, we'll only see
> unescaped \s - so it *does* make sense to escape the \s (if the user
> knew, then too many escaped \s still work).
>
>> - 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?
>>
> With subversion for Windows, these \\s are not needed (but doesn't
> cause any break). The doubling is something to do with the bash (in
> msys) I think.
>
Ok, so does that mean the logic should look more like the one you quoted
below without saying yes/no/anything? The points are:
(1) do not muck with SVN_SSH if already given by the user.
(2) when and only when we reuse value from GIT_SSH for SVN_SSH, double
the backslashes.
>> 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;
>> }
>> }
>> }
>>
>>
prev parent reply other threads:[~2009-08-18 19:25 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
2009-08-17 23:47 ` Karthik R
2009-08-18 5:48 ` Karthik R
2009-08-18 19:25 ` Junio C Hamano [this message]
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=7vk510diwa.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