All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
To: git@vger.kernel.org
Cc: peff@peff.net, sam@vilain.net
Subject: [PATCH v2 0/3] http: proxy support improvements
Date: Thu, 01 Mar 2012 19:16:20 +0100	[thread overview]
Message-ID: <4F4FBCF4.8010306@seap.minhap.es> (raw)

So here is v2 of proxy authentication support patch-set,
the following modifications were done as per discussion:

- PATCH 1/1: Extended commit message

- PATCH 2/2: Extended commit message and only read http_proxy
(discard HTTP_PROXY).

- PATCH 3/3: Extended commit message and use credential api for
retrieving password from user, taking care we only ask it once
for multiple curl handles case.

Nelson Benitez Leon (3):
  http: authenticate on NTLM proxies and others suppported by CuRL
  http: try http_proxy env var when http.proxy config option is not set
  http: when proxy url has username but no password, ask for password

 http.c |   27 +++++++++++++++++++++++++--
 1 files changed, 25 insertions(+), 2 deletions(-)

-- 
1.7.7.6

                 reply	other threads:[~2012-03-01 17:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F4FBCF4.8010306@seap.minhap.es \
    --to=nelsonjesus.benitez@seap.minhap.es \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=sam@vilain.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 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.