From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] git-repack: -b to pass --delta-base-offset
Date: Fri, 13 Oct 2006 17:58:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610131757050.2435@xanadu.home> (raw)
In-Reply-To: <7v64endi6x.fsf@assigned-by-dhcp.cox.net>
On Fri, 13 Oct 2006, Junio C Hamano wrote:
> Nicolas Pitre <nico@cam.org> writes:
>
> > On Thu, 12 Oct 2006, Junio C Hamano wrote:
> >
> >> This new option makes the resulting pack express the delta base
> >> with more compact "offset" format.
> >
> > Actually I thought about making it the default whenever git-pack-objects
> > supported it, and use a negative option with git-repack to disable it
> > instead.
> >
> > The fact is that there is little reason for not using delta base offsets
> > in most cases and specifying -b all the time would become more of an
> > annoyance.
> >
> > What do you think?
>
> The only time it matters is if the packs in repository being
> repacked needs to be readable by older git, which I think is
> only when somebody with older git uses commit walkers to
> download the pack into a remote repository to use. Using or not
> using delta-base-offset is tied to each repository, and in a
> sense that is similar to "repository format version".
>
> So how about
>
> [core]
> repackUseDeltaBase = true
I agree, although "repackUseDeltaBase" is a bit vague as both delta
types do use a delta base.
Nicolas
next prev parent reply other threads:[~2006-10-13 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 5:35 [PATCH 1/2] pack-objects: document --delta-base-offset option Junio C Hamano
2006-10-13 5:35 ` [PATCH 2/2] git-repack: -b to pass --delta-base-offset Junio C Hamano
2006-10-13 13:20 ` Nicolas Pitre
2006-10-13 13:51 ` Jakub Narebski
2006-10-13 21:22 ` Junio C Hamano
2006-10-13 21:29 ` Jakub Narebski
2006-10-13 21:58 ` Nicolas Pitre [this message]
2006-10-13 22:11 ` Junio C Hamano
2006-10-13 18:05 ` Horst H. von Brand
2006-10-13 18:29 ` Nicolas Pitre
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.0610131757050.2435@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).