From: Petr Baudis <pasky@ucw.cz>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Christopher Li <git@chrisli.org>, Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org
Subject: Re: CAREFUL! No more delta object support!
Date: Tue, 28 Jun 2005 22:30:04 +0200 [thread overview]
Message-ID: <20050628203004.GH1275@pasky.ji.cz> (raw)
In-Reply-To: <20050628163551.GA29410@kvack.org>
Dear diary, on Tue, Jun 28, 2005 at 06:35:51PM CEST, I got a letter
where Benjamin LaHaise <bcrl@kvack.org> told me that...
> On Tue, Jun 28, 2005 at 04:52:56PM +0200, Petr Baudis wrote:
> > I think the git-*-pull tools are actually just fine. You will only need
> > to have some server-side CGI gadget to frontend the file, but we need
> > that anyway to make the pull reasonably effective.
>
> Not really -- the use of rsync for the objects fails horribly on slow
> links when the project scales in the number of commits. The rsync
> protocol has to transfer the names of each file and some information
> about it, and that information isn't delta compressed. This is where
> kernel.org is falling over, as well as what makes the kernel tree very
> painful to use over a dialup modem link.
Yes. But isn't that what I'm after all saying too? git-*-pull tools
shouldn't have that problem since they have much less overhead and only
pull stuff you need.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..
next prev parent reply other threads:[~2005-06-28 20:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 1:14 CAREFUL! No more delta object support! Linus Torvalds
2005-06-27 23:58 ` Christopher Li
2005-06-28 3:30 ` Linus Torvalds
2005-06-28 9:40 ` Junio C Hamano
2005-06-28 11:06 ` Christopher Li
2005-06-28 14:52 ` Petr Baudis
2005-06-28 16:35 ` Benjamin LaHaise
2005-06-28 20:30 ` Petr Baudis [this message]
2005-06-28 14:46 ` Jan Harkes
2005-06-28 10:38 ` Christopher Li
2005-06-28 16:45 ` Linus Torvalds
2005-06-29 0:49 ` [PATCH] Emit base objects of a delta chain when the delta is output Junio C Hamano
2005-06-28 2:01 ` CAREFUL! No more delta object support! Junio C Hamano
2005-06-28 2:03 ` [PATCH] Skip writing out sha1 files for objects in packed git Junio C Hamano
2005-06-28 2:43 ` Linus Torvalds
2005-06-28 3:33 ` Junio C Hamano
2005-06-28 15:45 ` Linus Torvalds
2005-06-28 2:13 ` CAREFUL! No more delta object support! Linus Torvalds
2005-06-28 2:32 ` Junio C Hamano
2005-06-28 2:37 ` [PATCH] Adjust to git-init-db creating $GIT_OBJECT_DIRECTORY/pack Junio C Hamano
2005-06-28 2:48 ` CAREFUL! No more delta object support! Linus Torvalds
2005-06-28 5:09 ` Daniel Barkalow
2005-06-28 15:49 ` Linus Torvalds
2005-06-28 16:21 ` Linus Torvalds
2005-06-28 17:04 ` Daniel Barkalow
2005-06-28 17:36 ` Linus Torvalds
2005-06-28 18:17 ` Linus Torvalds
2005-06-28 19:49 ` Matthias Urlichs
2005-06-28 20:18 ` Matthias Urlichs
2005-06-28 20:01 ` Daniel Barkalow
2005-06-29 3:53 ` Linus Torvalds
2005-06-29 18:59 ` Linus Torvalds
2005-06-29 21:05 ` Daniel Barkalow
2005-06-29 21:38 ` Linus Torvalds
2005-06-29 22:24 ` Daniel Barkalow
2005-06-28 8:49 ` [PATCH] Adjust fsck-cache to packed GIT and alternate object pool Junio C Hamano
2005-06-28 21:56 ` [PATCH] Expose packed_git and alt_odb Junio C Hamano
2005-06-28 21:58 ` [PATCH 3/3] Update fsck-cache (take 2) 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=20050628203004.GH1275@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=bcrl@kvack.org \
--cc=git@chrisli.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).