All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Jeff King <peff@peff.net>
Cc: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>,
	Thomas Rast <trast@inf.ethz.ch>,
	git@vger.kernel.org, sam.vilain@catalyst.net.nz
Subject: Re: [PATCH 2/3] http: try standard proxy env vars when http.proxy config option is not set
Date: Tue, 28 Feb 2012 11:27:41 -0800	[thread overview]
Message-ID: <4F4D2AAD.3040107@vilain.net> (raw)
In-Reply-To: <20120228191514.GD11260@sigill.intra.peff.net>

On 2/28/12 11:15 AM, Jeff King wrote:
> Usually we would prefer environment variables to config. So that:
>
>    $ git config http.proxy foo
>    $ HTTP_PROXY=bar git fetch
>
> would use "bar" as the proxy, not "foo". But your code above would
> prefer "foo", right?

Apparently I'm the author of the http.proxy feature, though I barely 
remember what problem I was actually solving at the time.  At the time I 
justified it on the grounds that a user might want to use a different 
proxy for git and/or a particular remote.  The "http_proxy" environment 
variable is likely to be a global system default, or perhaps a desktop 
setting, and therefore I'd say probably less and not more specific than 
a git configuration variable.

As to this matter of "HTTP_PROXY", I'm not sure about whether that helps 
or confuses matters to support.  I must admit I'm still confused by the 
motivation of this patch series.

Sam

  reply	other threads:[~2012-02-28 19:27 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
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 [this message]
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=4F4D2AAD.3040107@vilain.net \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    --cc=nelsonjesus.benitez@seap.minhap.es \
    --cc=peff@peff.net \
    --cc=sam.vilain@catalyst.net.nz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.