From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Duffey, Blake" <Blake.Duffey@noblis.org>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: CTRL-C in ssh included with git kills the pipe
Date: Fri, 2 Jun 2023 22:52:00 +0000 [thread overview]
Message-ID: <ZHpykC3Cm+TzpSSa@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <45dd0347ff2646e8a9770644728afb07@BN2P110MB1224.NAMP110.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On 2023-06-02 at 21:55:21, Duffey, Blake wrote:
> The version of OpenSSH included with git 2.41 reports as:
> OpenSSH_9.3p1, OpenSSL 1.1.1u 30 May 2023
>
> The version of OpenSSH available from https://github.com/PowerShell/Win32-OpenSSH/releases reports as:
> OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2
>
> If I connect to server X with the first client, run top, and issue CTRL-C - I get
> client_loop: send disconnect: Broken pipe
>
> If I connect to server X with the second client, run top, and issue CTRL-C...
> it ends top and the connection remains
The Git project does not ship anything but source code. It sounds like
you're using Git for Windows, which does ship a variety of software,
including OpenSSH. Assuming that's the case, you may want to go to
their issue tracker, at https://github.com/git-for-windows/git/issues/,
to report this, after verifying that there's not already an issue for
this. That being said, it looks like
https://github.com/git-for-windows/git/issues/3848 may be the issue
you're reporting.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2023-06-02 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 21:55 CTRL-C in ssh included with git kills the pipe Duffey, Blake
2023-06-02 22:52 ` brian m. carlson [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=ZHpykC3Cm+TzpSSa@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Blake.Duffey@noblis.org \
--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.
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).