git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
Cc: Thomas Rast <trast@inf.ethz.ch>,
	git@vger.kernel.org, peff@peff.net, sam.vilain@catalyst.net.nz,
	sam@vilain.net
Subject: Re: [PATCH 2/3] http: try standard proxy env vars when http.proxy config option is not set
Date: Wed, 29 Feb 2012 10:15:37 -0800	[thread overview]
Message-ID: <7vlinltsja.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4F4E003C.1050301@seap.minhap.es> (Nelson Benitez Leon's message of "Wed, 29 Feb 2012 11:38:52 +0100")

Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es> writes:

> On 02/28/2012 08:24 PM, Junio C Hamano wrote:
>
>> I've heard rumors that libcurl on some versions/installations of Mac OS X
>> deliberately ignores the environment. For those who agree with Apple, it
>> would be a regression if we suddenly start the environment ourselves and
>> using it.
>
> Hi Junio, what did you mean by "we start the environment and using it"?
> I didn't understand what you mean there..

The reason you didn't understand is because the statement does not parse
X-<.  Thanks for pointing it out.

What I meant was that on these platforms, allegedly (note that I do not
have a first-hand experience with them), user's http_proxy environment
setting did not affect libcurl based applications and that is a deliberate
platform decision to give precedence to proxy settings the platform has
elsewhere.  The users who agree with this platform decision are happily
using the proxy settings stored elsewhere in the platform with git, but
may have http_proxy environment pointing at a proxy that they do not want
to use for git.

If we suddenly start reading from http_proxy environment ourselves and
explicitly telling libcurl to use the proxy specified, it will change the
behaviour for these users, i.e. a regression.

  reply	other threads:[~2012-02-29 18:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 12:54 [PATCH 2/3] http: try standard proxy env vars when http.proxy config option is not set Nelson Benitez Leon
2012-02-28 12:19 ` Thomas Rast
2012-02-28 14:57   ` Nelson Benitez Leon
2012-02-28 14:34     ` Thomas Rast
2012-02-28 19:24   ` Junio C Hamano
2012-02-29 10:38     ` Nelson Benitez Leon
2012-02-29 18:15       ` Junio C Hamano [this message]
2012-03-01 10:18         ` Nelson Benitez Leon
2012-03-04 19:19     ` Daniel Stenberg
2012-02-28 19:15 ` Jeff King
2012-02-28 19:27   ` Sam Vilain
2012-02-28 19:34     ` Jeff King
2012-02-29  9:55       ` Matthieu Moy
2012-02-29 10:46       ` Nelson Benitez Leon
2012-02-29 21:08         ` Jeff King
2012-03-01  9:57           ` Nelson Benitez Leon
2012-03-01  9:10             ` Jeff King
2012-03-11 16:56 ` James Cloos
2012-03-11 19:12   ` Junio C Hamano
2012-03-13 10:22     ` Nelson Benitez Leon
2012-03-14  4:36       ` Junio C Hamano
2012-03-14  9:54         ` Nelson Benitez Leon
2012-03-14 20:41           ` Junio C Hamano
2012-03-15  9:38             ` Nelson Benitez Leon

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=7vlinltsja.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nelsonjesus.benitez@seap.minhap.es \
    --cc=peff@peff.net \
    --cc=sam.vilain@catalyst.net.nz \
    --cc=sam@vilain.net \
    --cc=trast@inf.ethz.ch \
    /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 NNTP newsgroup(s).