git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Luc Herren <jlh@gmx.ch>
To: Jakub Narebski <jnareb@gmail.com>,
	Thanassis Tsiodras <ttsiodras@gmail.com>,
	git@vger.kernel.org
Subject: Re: Are binary xdeltas only used if you use git-gc?
Date: Fri, 31 Oct 2008 18:03:18 +0100	[thread overview]
Message-ID: <490B3A56.3040601@gmx.ch> (raw)
In-Reply-To: <m37i7pggnk.fsf@localhost.localdomain>

Jakub Narebski wrote:
> "Thanassis Tsiodras" <ttsiodras@gmail.com> writes:
>> Then again, I must confess I only did the git-gc after I pushed.
>> Does the git-push actually take advantage of the similarities only if
>> I do a git-gc first?
> 
> 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...

AFAICT, git stopped pushing thin packs by default with 1.5.3.2, so
you have to explicitely ask for it.  The original poster might not
be clear about this (or even know what a thin pack is).

Thanassis, try to use "git push --thin".  'man git-push' says:

  --thin, --no-thin
      These options are passed to git-send-pack. Thin transfer spends
      extra cycles to minimize the number of objects to be sent and meant
      to be used on slower connection.

I did a quick test with big random files and it indeed only sends
small deltas on small changes, but if you don't pass --thin, it
will send the full objects.

I didn't find a configuration variable to change that default.  It
would make sense for people that regularly push over slow lines.

Hope this helps,
jlh

  parent reply	other threads:[~2008-10-31 17:04 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
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 [this message]
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=490B3A56.3040601@gmx.ch \
    --to=jlh@gmx.ch \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=ttsiodras@gmail.com \
    /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).