From: Julian Phillips <julian@quantumfyre.co.uk>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Aubrey Li <aubreylee@gmail.com>, git@vger.kernel.org
Subject: Re: git clone problem through HTTP
Date: Fri, 20 Apr 2007 15:19:25 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0704201518170.3277@reaper.quantumfyre.co.uk> (raw)
In-Reply-To: <E27761F8-7325-433C-89BB-B3475FA802A3@silverinsanity.com>
On Fri, 20 Apr 2007, Brian Gernhardt wrote:
>
> On Apr 20, 2007, at 9:38 AM, Aubrey Li wrote:
>
>> On 4/20/07, Julian Phillips <julian@quantumfyre.co.uk> wrote:
>> > On Fri, 20 Apr 2007, Aubrey Li wrote:
>> >
>> > > I'm behind of a firewall on which the git port is not permitted, so I
>> > > can only use http protocol. Unfortunately, I can't clone linus' git
>> > > tree at all.
>> >
>> > Linus packs his refs, which means that currently you can't clone using
>> > http, with any version of git.
>>
>> I really don't understand why packed refs or not depend on the protocol.
>> It doesn't make any sense.
>
> I think it's simply because git-http-fetch doesn't look for the packed-refs
> file.
Yep.
> Are we actually going to support HTTP fetching? If so, we should
> update it to pull the packed-refs file too. If not, it should be clearly
> marked as depreciated. That said, I think HTTP is the easiest way for most
> people to publish and removing it would be a mistake. I'd poke at it, but
> there's not enough spare time in the day at the moment.
I was hoping to find time to poke this over the weekend ... maybe even
this evening.
--
Julian
---
Nature always sides with the hidden flaw.
next prev parent reply other threads:[~2007-04-20 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 7:15 git clone problem through HTTP Aubrey Li
2007-04-20 11:48 ` Julian Phillips
2007-04-20 13:01 ` Medve Emilian-EMMEDVE1
2007-04-20 13:38 ` Aubrey Li
2007-04-20 13:59 ` Alex Riesen
2007-04-20 14:01 ` Brian Gernhardt
2007-04-20 14:19 ` Julian Phillips [this message]
2007-04-20 21:02 ` Junio C Hamano
2007-04-20 21:09 ` Junio C Hamano
2007-04-20 21:31 ` Junio C Hamano
2007-04-22 5:10 ` Aubrey Li
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=Pine.LNX.4.64.0704201518170.3277@reaper.quantumfyre.co.uk \
--to=julian@quantumfyre.co.uk \
--cc=aubreylee@gmail.com \
--cc=benji@silverinsanity.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).