git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Ken.Fuchs@bench.com
Cc: git@vger.kernel.org
Subject: RE: FW: git via http protocol _and_ a proxy using NTLM authentication -- git 1.5.4.2 & curl 7.18.0
Date: Fri, 29 Feb 2008 00:59:58 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LSU.1.00.0802290057230.22527@racer.site> (raw)
In-Reply-To: <AA28F077645B324881335614E4F7C428034C11@win-ex01.bench.com>

Hi,

On Thu, 28 Feb 2008, Ken.Fuchs@bench.com wrote:

> On Wed, 27 Feb 2008, Johannes Schindelin wrote:
> 
> > On Wed, 27 Feb 2008, Ken Fuchs wrote:
> > 
> > [Ken did not say who said this:]
> 
> Sorry, Mike Hommey wrote the following on 27 Feb 2008:
> 
> > > > git-clone is not a builtin yet. When it is (and a patch 
> > > > has come for that), it will correctly use proxys.
> > > 
> > > Is there a work-around for cloning a git repository via a proxy?
> 
> > Yes.
> > 
> > Just export "http_proxy".  AFAICT this works... See
> > 
> >
> http://repo.or.cz/w/msysgit.git?a=commitdiff;h=257a62710c0253d940a59b6fb
> 2f371afa84dcf56
> 
> > for a working example.
> 
> Unfortunately, this will not work because "git clone" is
> implemented by git-clone.sh and has no support for dealing
> with proxies at all.

I fail to see why git-clone.sh, which uses git http-fetch directly, should 
behave differently from git fetch, which uses git http-fetch directly.

I strongly suspect that you did not even try what I suggested.

> So it seems that git's http protocol via a proxy isn't completely 
> supported.

If that should really be the case, well, Git is a programmers' tool, so 
you should be perfectly able to find out what is happening _exactly_.

If not, well, I heard subversion and Mercurial have nice Windows support.

Ciao,
Dscho


  reply	other threads:[~2008-02-29  1:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 22:04 FW: git via http protocol _and_ a proxy using NTLM authentication -- git 1.5.4.2 & curl 7.18.0 Ken.Fuchs
2008-02-29  0:59 ` Johannes Schindelin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-29 20:06 Ken.Fuchs
2008-02-29 20:32 ` Mike Hommey
2008-02-27 23:43 Ken.Fuchs
2008-02-28  0:10 ` Johannes Schindelin
2008-02-26 23:46 Ken.Fuchs
2008-02-27  7:20 ` Mike Hommey
2008-02-27  7:29   ` Mike Hommey
2008-02-26 21:43 Ken.Fuchs
2008-02-26 22:01 ` Daniel Stenberg

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=alpine.LSU.1.00.0802290057230.22527@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=Ken.Fuchs@bench.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public 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).