On Fri, 6 Apr 2007, Junio C Hamano wrote:
David Lang <david.lang@xxxxxxxxxxxxxxxxxx> writes:
On Fri, 6 Apr 2007, Junio C Hamano wrote:
Subject: Re: git-index-pack really does suck..
Junio C Hamano <junkio@xxxxxxx> writes:
David Lang <david.lang@xxxxxxxxxxxxxxxxxx> writes:
On Wed, 4 Apr 2007, Alex Riesen wrote:
...
You never know what pull is networked (or should I say: remote enough
to cause a collision).
so leave it on for all pulls, but for other commands don't turn it on.
remember that the command that linus ran into at the start of the
thread wasn't a pull.
Are you referring to this command
$ git index-pack --stdin --fix-thin new.pack < .git/objects/pack/pack-*.pack
in this message?
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Subject: git-index-pack really does suck..
Date: Tue, 3 Apr 2007 08:15:12 -0700 (PDT)
Message-ID: <Pine.LNX.4.64.0704030754020.6730@xxxxxxxxxxxxxxxxxxxxxxxxxx>
(sorry, chomped the message).
probably (I useually don't keep the mail after I read or reply to it)
Well, then you should remember that the command linus ran into
was pretty much about pull, nothing else.
The quoted command was only to illustrate what 'git-pull'
invokes internally. I do not think of any reason to use that
command for cases other than 'git-pull'. What's the use case
you have in mind to run that command outside of the context of
git-pull?
I guess I'm not remembering the thread accurately then (and/or am mising it up
with a different thread). I thought that Linus had identified other cases that
were impacted (something about proving that the object doesn't exist)
David Lang
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html