All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Sasha Khapyorsky <sashak@voltaire.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Trivial support for cloning and fetching via ftp://.
Date: Wed, 13 Sep 2006 23:57:59 -0700	[thread overview]
Message-ID: <7vk6475408.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060914022404.GA900@sashak.voltaire.com> (Sasha Khapyorsky's message of "Thu, 14 Sep 2006 05:24:04 +0300")

Sasha Khapyorsky <sashak@voltaire.com> writes:

> This adds trivial support for cloning and fetching via ftp://.

Interesting.

I was wondering myself if our use of curl libraries in
http-fetch allows us to do this when I was looking at the
alternates breakage yesterday.

At a few places we do look at http error code that is returned
from the curl library, and change our behaviour based on that.
But it appears the difference between error code from ftp and
http has no bad effect on us.  In an empty repository, we can
run this:

	$ git-http-fetch -a -v heads/merge \
	  ftp://ftp.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git

(of course, this should normally be with http://www.kernel.org).
We notice that we get an error from a request for one object,
and switch to pack & alternates transfer.  The only difference
between http://www and ftp://ftp is that for the former we know
error code 404 and supress the error message but for the latter
we do not treat error 550 from RETR response any specially and
show an error message.  We still fall back to retrieve packs,
hoping that the missing object is in a pack.

I'd take this patch as is, but we might want to add some error
message supression logic just like we do for http.

  reply	other threads:[~2006-09-14  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  2:24 [PATCH] Trivial support for cloning and fetching via ftp:// Sasha Khapyorsky
2006-09-14  6:57 ` Junio C Hamano [this message]
2006-09-16  2:37   ` Sasha Khapyorsky
2006-09-16  9:12     ` Junio C Hamano
2006-09-16 10:01       ` Sasha Khapyorsky
2006-09-16 10:51         ` Sasha Khapyorsky
2006-09-16 17:29         ` Junio C Hamano
2006-09-16 17:41           ` Sasha Khapyorsky
2006-09-16 17:58             ` Junio C Hamano
2006-09-16 18:00               ` Junio C Hamano
2006-09-16 19:54                 ` Sasha Khapyorsky

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=7vk6475408.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=sashak@voltaire.com \
    /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.