From: Philip Oakley Date: Wed, 10 Oct 2012 22:32:00 GMT Subject: Re: Is anyone working on a next-gen Git protocol? Message-ID: <4CD4F3E1194047F5B91D4D4E1CE146AC@PhilipOakley> In-Reply-To: <7vlifeawd5.fsf@alter.siamese.dyndns.org> From: "Junio C Hamano" > Steffen Prohaska writes: > >> I've recently discovered that the current protocol can be amazingly >> inefficient when it comes to transferring binary objects. Assuming >> two >> repositories that are in sync. After a 'git checkout --orphan && git >> commit', a subsequent transfers sends all the blobs attached to the >> new >> commit, although the other side already has all the blobs. > > I do not think it has anything to do with binary, but what you > deserve from using orphan, where you declared that the history does > not have anything to do with the original. > > If both of your repositories had the two paralle lines of these > histories as branches, the transfer would have went well with or > without binary objects. > -- Steffen, An alternative could be a shallow clone for just those branches with the binary objects, so that the git objects are still identical. Or use a replace/graft to trim the line of development. It's still a fudge, but something you could look at.