From: "Thanassis Tsiodras" <ttsiodras@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Matthieu Moy" <Matthieu.Moy@imag.fr>,
"Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: Are binary xdeltas only used if you use git-gc?
Date: Sat, 1 Nov 2008 13:54:53 +0200 [thread overview]
Message-ID: <f1d2d9ca0811010454u203a7c88x1e09735b3fc1358f@mail.gmail.com> (raw)
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:
> 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
next prev parent reply other threads:[~2008-11-01 11:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 9:43 Are binary xdeltas only used if you use git-gc? Thanassis Tsiodras
2008-10-31 11:02 ` Pierre Habouzit
2008-10-31 11:16 ` Thanassis Tsiodras
2008-10-31 19:47 ` Nicolas Pitre
2008-10-31 19:31 ` Nicolas Pitre
2008-10-31 11:15 ` Jakub Narebski
2008-10-31 11:28 ` Thanassis Tsiodras
2008-10-31 16:26 ` Jakub Narebski
2008-10-31 16:42 ` Matthieu Moy
2008-10-31 19:53 ` Nicolas Pitre
2008-11-01 11:54 ` Thanassis Tsiodras [this message]
2008-11-01 13:25 ` Nicolas Pitre
2008-11-03 20:35 ` Thanassis Tsiodras
2008-11-03 20:52 ` Pieter de Bie
2008-11-03 21:42 ` Nicolas Pitre
2008-11-03 22:53 ` Thanassis Tsiodras
2008-11-04 1:18 ` Nicolas Pitre
2008-11-04 1:36 ` Junio C Hamano
2008-11-04 1:57 ` Nicolas Pitre
2008-11-04 3:17 ` Junio C Hamano
2008-10-31 17:03 ` Jean-Luc Herren
2008-10-31 12:42 ` Matthieu Moy
2008-10-31 14:22 ` Thanassis Tsiodras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1d2d9ca0811010454u203a7c88x1e09735b3fc1358f@mail.gmail.com \
--to=ttsiodras@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=nico@cam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).