Re: [PATCH] rev-list: add "--full-objects" flag.

From: Junio C Hamano <junkio@cox.net>
Date: Jul 10, 2005, 06:28 UTC
Message-ID: <7veka7uqcr.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.58.0507092206480.17536@g5.osdl.org>

>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
>> On Sat, 9 Jul 2005, Eric W. Biederman wrote:
>> I assume the commit graph information will be fairly modest.

That is true. My experience from the one I have been cooking, Gitified 2.4.0->2.6.12-rc2 BKCVS export results in a bit shy of 600KB commit ancestry information. The full development trail for that repository contains 370152 objects among which 28237 are commits; when packed into one pack-idx pair, it is around a 170MB .pack with a 9MB .idx file.

LT> But a _truly_ dumb server (ie one with no CGI at all, just "raw data", you LT> really end up with just effectively rsyncing it. Yes, you could create a LT> new "commit index file" every time you push, and maybe it's worth it, but LT> on the other hand, what's wrong with just rsyncing it all and parsing it LT> locally instead?

Nothing, and you convinced me to drop the one I have been cooking. Maybe its time to either change git-fetch-script to use wget -r for http transport for objects part, perhaps?