From: Junio C Hamano <junkio@cox.net>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: git@vger.kernel.org
Subject: Re: Last mile to 1.0?
Date: Sat, 16 Jul 2005 17:49:57 -0700 [thread overview]
Message-ID: <7vy8869ryi.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <m18y06pphg.fsf@ebiederm.dsl.xmission.com> (Eric W. Biederman's message of "Sat, 16 Jul 2005 12:36:43 -0600")
ebiederm@xmission.com (Eric W. Biederman) writes:
> Junio C Hamano <junkio@cox.net> writes:
>>
>> - Anonymous pull from packed archives on remote sites via
>> non-rsync, non-ssh transport. ...
>> ... but we may also end up wanting something HTTP
>> reachable.
>
> For this we need a cgi script that will generate an appropriate
> pack.
I agree that nothing would beat a pack customized for each
puller from the bandwidth point of view. I like the general
idea of git-daemon Linus did and the cgi script you suggest, but
I wonder what the CPU/disk load implications for the server.
next prev parent reply other threads:[~2005-07-17 0:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:46 Last mile to 1.0? Junio C Hamano
2005-07-16 18:36 ` Eric W. Biederman
2005-07-17 0:49 ` Junio C Hamano [this message]
2005-07-17 1:18 ` David Lang
2005-07-18 5:44 ` Junio C Hamano
2005-07-18 4:53 ` Alexey Nezhdanov
2005-07-18 5:35 ` Junio C Hamano
2005-07-18 6:48 ` Alexey Nezhdanov
2005-07-18 7:38 ` Junio C Hamano
2005-07-23 8:15 ` Ryan Anderson
2005-07-23 12:56 ` Gene Heskett
2005-07-24 0:53 ` [PATCH 0/6] A bit better dumb server support Junio C Hamano
2005-07-23 8:50 ` Last mile to 1.0? Ryan Anderson
2005-07-23 13:14 ` Gene Heskett
2005-07-23 14:47 ` Kevin Smith
2005-07-23 17:09 ` Junio C Hamano
2005-07-24 3:12 ` Alexey Nezhdanov
2005-07-29 22:41 ` Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 5:40 barkalow
2005-07-30 8:07 ` 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=7vy8869ryi.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ebiederm@xmission.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.
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).