From: Daniel Barkalow <barkalow@iabervon.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Martin Langhoff <martin@catalyst.net.nz>, git@vger.kernel.org
Subject: Re: [RFC] git-fetch - repack in the background after fetching
Date: Tue, 30 May 2006 02:37:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605300207130.6713@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0605292147010.5623@g5.osdl.org>
On Mon, 29 May 2006, Linus Torvalds wrote:
> Some long-running (in git terms) git programs will look up the pack-files
> when they start, and if you repack after that, they won't see the new
> pack-file, but they _will_ notice that the unpacked files are no longer
> there, and will be very unhappy indeed.
We should be able to fix this, right? If an object isn't found in packs or
unpacked, look for new packs; if there are any, look for the object in
them; if it's not there, then give up. The only tricky thing is making it
possible to scan through the available packs without installing any that
are already installed. I think the failure case is only a critical path in
the history-walking fetch code, which should probably disable this (or
defer it to after trying to download the object).
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2006-05-30 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 4:42 [RFC] git-fetch - repack in the background after fetching Martin Langhoff
2006-05-30 4:51 ` Linus Torvalds
2006-05-30 5:14 ` Martin Langhoff
2006-05-30 6:37 ` Daniel Barkalow [this message]
2006-05-30 14:53 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-06-24 11:30 Martin Langhoff
2006-06-25 3:12 ` Junio C Hamano
2006-06-25 3:53 ` Linus Torvalds
2006-06-25 9:25 ` Johannes Schindelin
2006-06-25 17:29 ` Linus Torvalds
2006-06-25 17:53 linux
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.0605300207130.6713@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
--cc=torvalds@osdl.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).