From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [BUG] GIT_SSH_COMMAND is not being decomposed
Date: Sat, 13 Apr 2019 16:27:44 -0400 [thread overview]
Message-ID: <000d01d4f237$5cf2dc10$16d89430$@nexbridge.com> (raw)
I am encountering a problem on one of our NonStop platform variants where
the GIT_SSH_COMMAND string is not being broken into constituent parts. This
is causing SSH to not run properly. As background, SSH is not in a standard
location and has non-standard required arguments. This also occurs with
core.sshCommand. The situation is:
git config --global core.sshCommand '/G/system/zssh/sshossz5 -Q'
which correctly sets .gitconfig as:
[core]
sshCommand = /G/system/zssh/sshossz5 -Q
When git is run with GIT_TRACE=true GIT_PACKET_TRACE=true git fetch
We get the partial trace:
14:19:56.027088 trace: built-in: git fetch
14:19:56.029895 trace: run_command: '/G/system/zssh/sshossz5 -Q' -G
user@host
The same trace on our systems that actually do work results in:
14:19:56.029895 trace: run_command: '/G/system/zssh/sshossz5' '-Q' -G
user@host
I need help resolving why this is happening (as in where to look and debug
the situation).
Urgently,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next reply other threads:[~2019-04-13 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 20:27 Randall S. Becker [this message]
2019-04-13 20:39 ` [BUG] GIT_SSH_COMMAND is not being decomposed Ævar Arnfjörð Bjarmason
2019-04-13 20:57 ` Randall S. Becker
2019-04-13 21:47 ` SZEDER Gábor
2019-04-14 14:34 ` Randall S. Becker
2019-04-15 19:20 ` Randall S. Becker
2019-04-15 21:14 ` Andreas Schwab
2019-04-15 22:34 ` Randall S. Becker
2019-04-16 4:24 ` Junio C Hamano
2019-04-15 21:30 ` Johannes Sixt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000d01d4f237$5cf2dc10$16d89430$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).