From: Elijah Newren <newren@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [Patch 1/3] connect.c: add nonstopssh variant to the sshVariant set.
Date: Fri, 30 Apr 2021 09:25:29 -0700 [thread overview]
Message-ID: <CABPp-BH6RgiMwGLz31nHmis3VTpuEUG--G_6Y+Wfwg24u4Zbag@mail.gmail.com> (raw)
In-Reply-To: <011f01d73dd0$ecf91e00$c6eb5a00$@nexbridge.com>
On Fri, Apr 30, 2021 at 7:58 AM Randall S. Becker
<rsbecker@nexbridge.com> wrote:
>
> From ba4beb8ed0dff67ae6b95692d346adce346e2871 Mon Sep 17 00:00:00 2001
> From: "Randall S. Becker" <rsbecker@nexbridge.com>
> Date: Fri, 30 Apr 2021 09:56:09 -0400
> Subject: [Patch 1/3] connect.c: add nonstopssh variant to the sshVariant set.
>
> This enhancement allows the NonStop SSH subsystem to be supported by
> git without the need of a wrapper script. The command arguments for
> the platform SSH client in /G/system/zssh/sshoss are constructed based
> on optional supplied environment variables SSH2_PROCESS_NAME (system
> defined), SSH_SUPPRESS_QUIET, and SSH_SUPPRESS_BANNER.
Before introducing 3 new special environment variables, I think this
commit message should explain why you can't just use
GIT_SSH_COMMAND="/G/system/zssh/sshoss -Z -Q -S"
particularly since GIT_SSH_COMMAND was introduced specifically so
people wouldn't have to create wrapper scripts to pass to GIT_SSH.
next prev parent reply other threads:[~2021-04-30 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 14:55 [Patch 1/3] connect.c: add nonstopssh variant to the sshVariant set Randall S. Becker
2021-04-30 16:25 ` Elijah Newren [this message]
2021-04-30 16:38 ` Randall S. Becker
2021-04-30 17:17 ` Elijah Newren
2021-04-30 17:32 ` Randall S. Becker
2021-05-10 15:24 ` Randall S. Becker
2021-06-04 19:29 ` Randall S. Becker
2021-06-04 19:51 ` Junio C Hamano
2021-06-04 20:35 ` Randall S. Becker
2021-06-05 21:56 ` Randall S. Becker
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=CABPp-BH6RgiMwGLz31nHmis3VTpuEUG--G_6Y+Wfwg24u4Zbag@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
/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).