git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: git@vger.kernel.org
Subject: Re: HTTP redirection with git-clone/git-fetch ?
Date: Thu, 10 Nov 2005 14:09:48 +0100	[thread overview]
Message-ID: <200511101409.48618.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <20051110002419.GB4051@reactrix.com>

On Thursday 10 November 2005 01:24, Nick Hengeveld wrote:
> On Wed, Nov 09, 2005 at 11:31:36PM +0100, Josef Weidendorfer wrote:
> 
> > This seems because git-fetch should understand redirections, too.
> > I am not familiar to the curl API. So perhaps another one can try to
> > fix this?
> 
> This should fix it, although it still tries every GET with the original
> URL which is a bit inefficient.

Thanks, I just sent a patch for git-clone, including your patch, to
Junio.

Josef

  reply	other threads:[~2005-11-10 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 22:31 HTTP redirection with git-clone/git-fetch ? Josef Weidendorfer
2005-11-10  0:24 ` Nick Hengeveld
2005-11-10 13:09   ` Josef Weidendorfer [this message]
2005-11-11 17:38     ` Junio C Hamano

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=200511101409.48618.Josef.Weidendorfer@gmx.de \
    --to=josef.weidendorfer@gmx.de \
    --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.
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).