mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: "H.J. Lu" <>
Subject: Re: Commit ae1a7eefff may have broken git behind a firewall
Date: Tue, 12 Oct 2021 17:17:37 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Oct 12, 2021 at 02:03:39PM -0700, H.J. Lu wrote:

> may have broken git behind a firewall:
> I am behind a firewall and using gitproxy:
> exec socat - socks4:proxy-server-name:$1:$2

It's not the firewall; it's socat not handling half-duplex shutdown very
well (though you are right that it is related to the commit you found;
that's when Git started closing the write pipe when it's done writing).

More discussion in this thread:

(the short answer is: use "socat -t 10").


  reply	other threads:[~2021-10-12 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 21:03 Commit ae1a7eefff may have broken git behind a firewall H.J. Lu
2021-10-12 21:17 ` Jeff King [this message]
2021-10-12 21:41   ` H.J. Lu

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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

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).