From: Tay Ray Chuan <rctay89@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, msysgit@googlegroups.com,
Tom Preston-Werner <tom@mojombo.com>
Subject: Re: Issue 323 in msysgit: Can't clone over http
Date: Tue, 8 Sep 2009 21:10:21 +0800 [thread overview]
Message-ID: <be6fef0d0909080610j89c0a4bkf1cb0119b9b11db@mail.gmail.com> (raw)
In-Reply-To: <7v7hwatw0v.fsf@alter.siamese.dyndns.org>
Hi,
On Tue, Sep 8, 2009 at 3:06 AM, Junio C Hamano<gitster@pobox.com> wrote:
> I am torn about this.
>
> On one hand, if we are going to treat such a half failure as nothing
> conclusive, I do not see a point to keep that check to begin with.
>
> On the other hand, if a HEAD request to a URL results in an unauthorized,
> what plausible excuse the server operator could give for allowing a GET
> request to the same URL? If we are going to keep the check if *.pack that
> corresponds to the *.idx will be available, shouldn't we trust whatever
> check we perform?
I am in favour or removing this check, not just due to its
unreliability, but for the sake of consistency (we very rarely send a
HEAD request to poll data before doing a GET).
Do disregard the patch included earlier, if you haven't already done so.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2009-09-08 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0016e6470f36315b8a0472bc75a8@google.com>
2009-09-04 10:25 ` Issue 323 in msysgit: Can't clone over http Junio C Hamano
2009-09-04 13:29 ` Tay Ray Chuan
2009-09-07 4:59 ` Junio C Hamano
2009-09-07 5:53 ` Tay Ray Chuan
2009-09-07 7:10 ` Junio C Hamano
2009-09-07 8:18 ` Junio C Hamano
2009-09-07 9:27 ` Tay Ray Chuan
2009-09-07 19:06 ` Junio C Hamano
2009-09-08 12:57 ` Jakub Narebski
2009-09-08 13:18 ` Tay Ray Chuan
2009-09-08 13:10 ` Tay Ray Chuan [this message]
2009-09-09 12:33 ` Tay Ray Chuan
2009-09-09 19:08 ` Junio C Hamano
2009-09-11 8:54 ` Junio C Hamano
2009-09-12 10:01 ` Tay Ray Chuan
2009-09-12 17:31 ` 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=be6fef0d0909080610j89c0a4bkf1cb0119b9b11db@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.com \
--cc=tom@mojombo.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 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).