Re: Are binary xdeltas only used if you use git-gc?

From: Jakub Narebski <jnareb@gmail.com>
Date: Oct 31, 2008, 16:26 UTC
Message-ID: <200810311726.57122.jnareb@gmail.com>
In-Reply-To: <f1d2d9ca0810310428o166dc075wbb43c00c1a555350@mail.gmail.com>

Thanassis Tsiodras wrote:

> On Fri, Oct 31, 2008 at 1:15 PM, Jakub Narebski <jnareb@gmail.com> wrote:

Show 8 quoted lines

> > Git does deltification _only_ in packfiles. But when you push via SSH
> > git would generate a pack file with commits the other side doesn't
> > have, and those packs are thin packs, so they also have deltas... but
> > the remote side then adds bases to those thin packs making them
> > standalone: you would have to git-gc on remote.
> 
> So I have to git-gc on my side (after the commits), git-gc on the remote,
> and then git-push?

Perhaps I haven't made myself clear.

On the local side: git-commit creates loose (compressed, but not deltified) objects. git-gc packs and deltifies.

On the remote side (for smart protocols, i.e. git and ssh): git creates _thin_ pack, deltified; on the remote side git either makes pack thick/self contained by adding base objects (object + deltas), or explodes pack into loose object (object). You need git-gc on remote server to fully deltify on remote side. But transfer is fully deltified.

On the remote side (for dumb protocols, i.e. rsync and http): git finds required packs and transfers them whole. So the situation is like on local side, but git might transfer more than really needed because it transfers packs in full.

HTH.

-- 
Jakub Narebski
Poland