From: "H.J. Lu" <email@example.com> To: Jeff King <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Commit ae1a7eefff may have broken git behind a firewall Date: Tue, 12 Oct 2021 14:41:20 -0700 [thread overview] Message-ID: <CAMe9rOqQxk3cfxvJiJQRoG5=KVn2SkPbZKVa+w4MZP56OA-Z1g@mail.gmail.com> (raw) In-Reply-To: <YWX7cd5e5q84CDEv@coredump.intra.peff.net> On Tue, Oct 12, 2021 at 2:17 PM Jeff King <firstname.lastname@example.org> wrote: > > On Tue, Oct 12, 2021 at 02:03:39PM -0700, H.J. Lu wrote: > > > https://github.com/git/git/commit/ae1a7eefff > > > > may have broken git behind a firewall: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2013288 > > > > 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: > > https://lore.kernel.org/git/YS1Bni+QuZBOgkUI@coredump.intra.peff.net/ > > (the short answer is: use "socat -t 10"). > > -Peff Yes, "socat -t 10" works. Thanks. -- H.J.
prev parent reply other threads:[~2021-10-12 21:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-12 21:03 H.J. Lu 2021-10-12 21:17 ` Jeff King 2021-10-12 21:41 ` H.J. Lu [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 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='CAMe9rOqQxk3cfxvJiJQRoG5=KVn2SkPbZKVa+w4MZP56OA-Z1g@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Commit ae1a7eefff may have broken git behind a firewall' \ /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
Code repositories for project(s) associated with this 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).