From: Andreas Ericsson <ae@op5.se>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Nick Hengeveld <nickh@reactrix.com>,
Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc2
Date: Fri, 25 Nov 2005 09:42:16 +0100 [thread overview]
Message-ID: <4386CE68.1020200@op5.se> (raw)
In-Reply-To: <200511242151.00162.tomlins@cam.org>
Ed Tomlinson wrote:
> On Thursday 24 November 2005 14:52, Nick Hengeveld wrote:
>
>>On Thu, Nov 24, 2005 at 10:37:15AM -0800, Linus Torvalds wrote:
>>
>>
>>>I just repacked and updated it now, so how http should work too, although
>>>inefficiently (because it will get a whole new pack - just one of the
>>>disadvantages of the non-native protocols).
>>
>>There's room to improve on that particular inefficiency. The http
>>commit walker could use Range: headers to fetch loose objects directly
>>from inside a pack if it didn't make sense to fetch the entire pack.
>>For this to work, pack fetches would need to be deferred until the
>>entire tree had been walked, and the commit walker could decide whether
>>to fetch the pack or loose objects based on the percentage of packed
>>objects it needed to fetch. It would also need to fetch all
>>tag/commit/tree objects using ranges to be able to fully walk the tree.
>
>
> Alternately, when creating a new archive the client could ask the server
> what protocols are active. It could then use the best one for the clone and
> update the .git/origin files with the optimal one for incremental pulls.
>
This would only work with the git protocol, and since that's the fastest
protocol (theoretically that is, Pasky seems to have gotten other
figures but I'm not sure I believe those) it should really only ever
return itself which wouldn't make much sense.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2005-11-25 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0511191934210.8552@g5.osdl.org>
2005-11-24 12:37 ` Linux 2.6.15-rc2 Ed Tomlinson
2005-11-24 13:07 ` Andreas Ericsson
2005-11-24 18:44 ` Linus Torvalds
2005-11-24 19:42 ` Junio C Hamano
2005-11-24 19:57 ` Linus Torvalds
2005-11-24 21:02 ` Junio C Hamano
2005-11-24 18:37 ` Linus Torvalds
2005-11-24 19:52 ` Nick Hengeveld
2005-11-25 2:50 ` Ed Tomlinson
2005-11-25 8:42 ` Andreas Ericsson [this message]
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=4386CE68.1020200@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nickh@reactrix.com \
--cc=tomlins@cam.org \
--cc=torvalds@osdl.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).