git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] pack-objects: use of version 3 delta is now optional.
Date: Mon, 16 Oct 2006 09:43:04 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610160929450.17085@xanadu.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0610151150530.3952@g5.osdl.org>

On Sun, 15 Oct 2006, Linus Torvalds wrote:

> 
> 
> On Sun, 15 Oct 2006, Junio C Hamano wrote:
> > 
> > I think that is sensible.  I also was thinking that we should
> > call the current one packv3 and the one with delta-base-offset
> > packv4.
> 
> Quite frankly, I wonder if the pure "copy size extension" (aka "v3") thing 
> is really worth it at all. 
> 
> I mean, seriously, how much does it buy us? A couple of bytes per every 
> 64kB of delta copied? And the downside is that you can't re-use the deltas 
> with old clients and/or you have to re-create a "v2" delta at run-time 
> from a v3 delta by inflating, fixing and deflating it.

Right.  This is why I suggested Junio to just drop it for now.  Let's 
just wait some more until this is just not an issue any longer, say in a 
year from now when all major distributions have switched to a GIT 
version that can read V3.

If until then we find the saving really worth the backward compatibility 
v3-to-v2 conversion then we could reconsider.  But I don't think it is 
worth it just yet.

In the mean time, if Junio adds the patch I posted yesterday advertising 
the pack version capability over the native protocol then it'll help us 
make things forward compatible if ever we decide to go with generating 
packs v3 sooner.


Nicolas

  reply	other threads:[~2006-10-16 13:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15  6:29 Recent and near future backward incompatibilities Junio C Hamano
2006-10-15  7:44 ` [PATCH] pack-objects: use of version 3 delta is now optional Junio C Hamano
2006-10-15  9:09   ` Jakub Narebski
2006-10-15 15:53   ` Nicolas Pitre
2006-10-15 18:10     ` Junio C Hamano
2006-10-15 18:18       ` Jakub Narebski
2006-10-15 18:51         ` Nicolas Pitre
2006-10-16  4:45           ` Junio C Hamano
2006-10-16 13:27             ` Nicolas Pitre
2006-10-15 18:30       ` Nicolas Pitre
2006-10-15 20:00         ` A Large Angry SCM
2006-10-16  2:52           ` Nicolas Pitre
2006-10-15 18:57       ` Linus Torvalds
2006-10-16 13:43         ` Nicolas Pitre [this message]
2006-10-17 16:12           ` Junio C Hamano
2006-10-17 16:51             ` Nicolas Pitre
2006-10-15 19:29       ` A Large Angry SCM
2006-10-15 14:52 ` Recent and near future backward incompatibilities Horst H. von Brand
2006-10-15 15:34 ` Nicolas Pitre
2006-10-15 18:14   ` Junio C Hamano
2006-10-15 22:40 ` Theodore Tso
2006-10-15 23:52   ` Linus Torvalds
2006-10-16  2:13     ` Stephen Hemminger

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=Pine.LNX.4.64.0610160929450.17085@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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).