Re: git-index-pack really does suck..
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Apr 3, 2007, 21:53 UTC
- Message-ID
- <20070403215342.GL27706@spearce.org>
- In-Reply-To
- <7vvegduo9e.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 13 quoted lines
> "Shawn O. Pearce" <spearce@spearce.org> writes: > > Here's the rub: in the missing object case we didn't find it > > in the pack index, but it could be loose. That's one failed > > syscall per object if the object isn't loose. If the object > > isn't loose, it could be that it was *just* removed by a > > running prune-packed, and the packfile that it was moved > > to was created after we scanned for packfiles, so time to > > rescan... > > If that is the only reason we have these reprepare_packed_git() > sprinkled all over in sha1_file.c (by 637cdd9d), perhaps we > should rethink that. Is there a cheap way to trigger these > rescanning only when a prune-packed is in progress, I wonder...
Yea, it is the only reason. So... if we could have some magic to trigger that, it would be good. I just don't know what magic that would be.
-- Shawn.