From: Junio C Hamano Date: Sun, 15 Jan 2006 21:15:59 GMT Subject: Re: dangling commits Message-ID: <7vslrp2nw0.fsf@assigned-by-dhcp.cox.net> In-Reply-To: Nick Williams writes: > Andreas Ericsson wrote: >.. >> Nopes. One clones over http, so you'll get all objects in the object >> database. The other clones over the far more clever git protocol >> which calculates which objects you need. Obviously you don't need >> dangling commits (and their related blobs), so there will be no such >> items. Note that only because that is these dangling objects are packed in the past, and when fetching over http, packs are fetched as a whole. > So, is there any advantage of using http? Seems like git:// makes more > sense. As long as you can go native git:// protocol, I do not see much reason to use http:// commit walkers. OTOH, if you are firewalled and your sysadmins do not let you pass 9418/tcp outgoing, HTTP might be your only choice.