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

From: Thanassis Tsiodras <ttsiodras@gmail.com>
Date: Nov 1, 2008, 11:54 UTC
Message-ID: <f1d2d9ca0811010454u203a7c88x1e09735b3fc1358f@mail.gmail.com>
In-Reply-To: <alpine.LFD.2.00.0810311549570.13034@xanadu.home>

Thanks to everybody for your help.

I will setup an alias to always use "git push --thin". For the reverse direction, I don't see a --thin for "git pull",

My understanding is that "git pull" is optimal, and does what --thin does for push anyway, right?

On 10/31/08, Nicolas Pitre <nico@cam.org> wrote:

Show 29 quoted lines

> On Fri, 31 Oct 2008, Matthieu Moy wrote:
>
>> Jakub Narebski <jnareb@gmail.com> writes:
>>
>> > Thanassis Tsiodras wrote:
>> >
>> >> 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;
>>
>> I don't understand this point: the OP talks about pushing, so isn't
>> the pack created on the _local_ machine (and then sent to the remote)?
>
> Yes, the pack is created on the fly when pushing, regardless if the repo
> is already packed or not locally.  The only difference a locally packed
> repo provides is a shorter "Compressing objects" phase when pushing
> that's all. The packedness of the remote has no effect at all.
>
>
> Nicolas
>

-- 
What I gave, I have; what I spent, I had; what I kept, I lost. -Old Epitaph