From: Jonathan Nieder <jrnieder@gmail.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Brandon Williams <bmwill@google.com>,
Ben Humphreys <behumphreys@atlassian.com>,
Git Users <git@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.16.0-rc0
Date: Tue, 2 Jan 2018 21:50:49 -0800 [thread overview]
Message-ID: <20180103055049.GC87855@aiede.mtv.corp.google.com> (raw)
In-Reply-To: <CAGyf7-EeBHwg50+MnUGF6=aE91TJY_iYSrg5gF1rp8ApsTsrvw@mail.gmail.com>
Bryan Turner wrote:
> On Tue, Jan 2, 2018 at 9:07 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> So my first question is why the basename detection is not working for
>> you. What value of GIT_SSH, GIT_SSH_COMMAND, or core.sshCommand are
>> you using?
>
> So I'd been digging further into this for the last hour because I
> wasn't seeing quite the behavior I was expecting when I ran Git from
> the command line on Ubuntu 12.04 or 14.04, and this nudged me to the
> right answer: We're setting GIT_SSH to a wrapper script. In our case,
> that wrapper script is just calling OpenSSH's ssh with all the
> provided arguments (plus a couple extra ones), but because we're
> setting GIT_SSH at all, that's why the auto variant code is running.
> That being the case, explicitly setting GIT_SSH_VARIANT=ssh may be the
> correct thing to do, to tell Git that we want to be treated like
> "normal" OpenSSH, as opposed to expecting Git to assume we behave like
> OpenSSH (when the Android repo use case clearly shows that assumption
> also doesn't hold).
Ah, that's a comfort. Setting GIT_SSH_VARIANT would avoid this
autodetection code and is the recommended thing to do.
That said, we can't go back in time and update everyone's tools to do
that (e.g. there is not even a release of repo with [1] out yet), so
this is still considered a regression and I'm glad you found it.
Jonathan
[1] https://gerrit-review.googlesource.com/c/git-repo/+/134950
next prev parent reply other threads:[~2018-01-03 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 4:30 [ANNOUNCE] Git v2.16.0-rc0 Junio C Hamano
2017-12-29 7:17 ` Kaartic Sivaraam
2018-01-03 3:34 ` Bryan Turner
2018-01-03 5:07 ` Jonathan Nieder
2018-01-03 5:41 ` Bryan Turner
2018-01-03 5:50 ` Jonathan Nieder [this message]
2018-01-03 5:35 ` Jonathan Nieder
2018-01-04 20:33 ` Johannes Schindelin
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=20180103055049.GC87855@aiede.mtv.corp.google.com \
--to=jrnieder@gmail.com \
--cc=behumphreys@atlassian.com \
--cc=bmwill@google.com \
--cc=bturner@atlassian.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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