From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: [PATCH] pack.indexversion config option now defaults to 2
Date: Wed, 25 Jun 2008 14:49:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806251442500.2979@xanadu.home> (raw)
In-Reply-To: <7vd4m66rfp.fsf@gitster.siamese.dyndns.org>
On Tue, 24 Jun 2008, Junio C Hamano wrote:
> For the other "usedeltabaseoffset" change, I think the insn in the
> documentation Nico added is reasonable:
>
> + By default, linkgit:git-repack[1] creates packs that use
> + delta-base offset. If you need to share your repository with
> + git older than version 1.4.4, either directly or via a dumb
> + protocol such as http, then you need to set this option to
> + "false" and repack. Access from old git versions over the
> + native protocol are unaffected by this option.
>
> except perhaps that the "set false and repack" should be clarified
> further, perhaps like:
>
> ... then you need to set this option to "false" and repack using
> git that is newer than (and including) v1.5.0.
Actually the first release to support this is v1.4.4 not v1.5.0.
> I am basing the above 1.5.0 on description of b6945f5 (git-repack:
> repo.usedeltabaseoffset, 2006-10-13).
$ git describe --contains b6945f5
v1.4.4-rc1~77^2~2
> On the "indexVersion" change, the documentation reads:
>
> pack.indexVersion::
> Specify the default pack index version. Valid values are 1 for
> legacy pack index used by Git versions prior to 1.5.2, and 2 for
> the new pack index with capabilities for packs larger than 4 GB
> as well as proper protection against the repacking of corrupted
> + packs. Version 2 is the default. Note that version 2 is enforced
> + and this config option ignored whenever the corresponding pack is
> + larger than 2 GB.
>
> which lacks the recovery insn (and it is int strictly the fault of this
> patch, but we should have done this when we introduced the v2 idx). I
> think a separate paragraph after the above would be necessary and
> sufficient:
>
> If you have an ancient git that does not understand the version 2
> `*.idx` file, cloning or fetching over a non native protocol
> (e.g. "http" and "rsync") which will copy both `*.pack` file and
> corresponding `*.idx` file from the other side may give you a
> repository that cannot be accessed with your old git. If the
> `*.pack` file is smaller than 2 GB, however, you can use
> `git-index-pack` on the `*.pack` to regenerate the `*.idx` file.
Looks fine to me. Will you amend the patches or do you want me to
repost them?
Nicolas
next prev parent reply other threads:[~2008-06-25 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 4:25 [PATCH] pack.indexversion config option now defaults to 2 Nicolas Pitre
2008-06-25 4:32 ` Linus Torvalds
2008-06-25 4:59 ` Junio C Hamano
2008-06-25 5:56 ` Mike Hommey
2008-06-25 6:06 ` Junio C Hamano
2008-06-25 6:14 ` Mike Hommey
2008-06-25 18:53 ` Nicolas Pitre
2008-06-25 18:58 ` Mike Hommey
2008-06-25 18:49 ` Nicolas Pitre [this message]
2008-06-25 19:19 ` Junio C Hamano
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=alpine.LFD.1.10.0806251442500.2979@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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).