Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
	"git@vger.kernel.org" <git@vger.kernel.org>,
	"greg.pflaum@pnp-hcl.com" <greg.pflaum@pnp-hcl.com>,
	"peff@peff.net" <peff@peff.net>
Subject: Re: Bug: Cloning git repositories behind a proxy using the git:// protocol broken since 2.32
Date: Tue, 31 Jan 2023 08:57:19 -0800	[thread overview]
Message-ID: <xmqqilgmzlow.fsf@gitster.g> (raw)
In-Reply-To: <339359ee8a228ea108109cf852bcb7e145807dcf.camel@siemens.com> (Florian Bezdeka's message of "Tue, 31 Jan 2023 13:08:40 +0100")

Florian Bezdeka <florian.bezdeka@siemens.com> writes:

> I guess proxy support was forgotten when the referenced change was
> made. Any chance we can avoid closing stdout when running "in proxy
> mode" to restore backward compatibility?

See the last paragraph of
https://lore.kernel.org/git/YS1Bni+QuZBOgkUI@coredump.intra.peff.net/

Nobody brought anything new to the table since then (the original
discussion was from Aug 2021) to change the conclusion that socat
was not doing the right thing in its default form.

Thanks.


  reply	other threads:[~2023-01-31 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 10:52 Bug: Cloning git repositories behind a proxy using the git:// protocol broken since 2.32 Bezdeka, Florian
2023-01-31 11:02 ` brian m. carlson
2023-01-31 12:08   ` Florian Bezdeka
2023-01-31 16:57     ` Junio C Hamano [this message]
2023-01-31 20:31     ` Jacob Keller
2023-01-31 23:19       ` Florian Bezdeka
2023-02-01 12:28         ` Jeff King
2023-02-01 12:53           ` Florian Bezdeka
2023-02-01 13:05             ` Bezdeka, Florian
2023-02-02  0:07             ` Jeff King

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=xmqqilgmzlow.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=git@vger.kernel.org \
    --cc=greg.pflaum@pnp-hcl.com \
    --cc=peff@peff.net \
    --cc=sandals@crustytoothpaste.net \
    /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