From: Mike Hommey <mh@glandium.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <gitster@pobox.com>,
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 20:58:54 +0200 [thread overview]
Message-ID: <20080625185854.GA4816@glandium.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0806251449530.2979@xanadu.home>
On Wed, Jun 25, 2008 at 02:53:41PM -0400, Nicolas Pitre wrote:
> On Wed, 25 Jun 2008, Mike Hommey wrote:
>
> > On Tue, Jun 24, 2008 at 09:59:06PM -0700, Junio C Hamano wrote:
> > > Linus Torvalds <torvalds@linux-foundation.org> writes:
> > >
> > > > On Wed, 25 Jun 2008, Nicolas Pitre wrote:
> > > >>
> > > >> Git older than version 1.5.2 (or any other git version with this option
> > > >> set to 1) may revert to version 1 of the pack index by manually deleting
> > > >> all .idx files and recreating them using 'git index-pack'. Communication
> > > >> over the git native protocol is unaffected since the pack index is never
> > > >> transferred.
> > > >
> > > > Rather than talk about when it does _not_ matter, wouldn't it be better to
> > > > talk about when it _can_ matter?
> > > >
> > > > Namely when using dumb protocols, either http or rsync, with the other end
> > > > being some ancient git thing (and it is worth mentioning version of what
> > > > counts as 'ancient' too, I can't remember, probably means that pretty much
> > > > nobody else can either).
> > >
> > > I agree with you that the description of the change (in the commit log)
> > > and the instruction (in the documentation) could be more helpful and
> > > explicit.
> > (...)
> >
> > Wouldn't it be a good idea to add a warning in git update-server-info
> > when it detects pack.indexVersion is not 1, too ?
>
> That would give the idea that index v2 is not good, while what we want
> is to encourage everyone to move to index v2 ASAP.
The warning could just say that people with older git won't be able to
clone over dumb protocols. Nothing more.
Mike
next prev parent reply other threads:[~2008-06-25 19:00 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 [this message]
2008-06-25 18:49 ` Nicolas Pitre
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=20080625185854.GA4816@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--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).