From: Junio C Hamano <junkio@cox.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] handle concurrent pruning of packed objects
Date: Fri, 02 Jun 2006 08:53:52 -0700 [thread overview]
Message-ID: <7vwtbzblkf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060602153223.GA4223@coredump.intra.peff.net> (Jeff King's message of "Fri, 2 Jun 2006 11:32:23 -0400")
Jeff King <peff@peff.net> writes:
> This is a repost, since there was no response last time. Linus
> indicated this approach was reasonable; see:
> <Pine.LNX.4.64.0605300752430.5623@g5.osdl.org>
I haven't forgotten about it, but I have been sick.
I am uncertain about not re-examining the packs it originally
thought it had. By prepending the new ones (and the same old
surviving ones) at the beginning you are effectively hiding the
old packs, which sounds reasonable in the usual case.
Also I suspect this might have funny interaction with the case
where there are hand-added packs (see how verify-pack does it).
We do not silently "fix" missing object problems we discover
there.
next prev parent reply other threads:[~2006-06-02 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 15:32 [PATCH] handle concurrent pruning of packed objects Jeff King
2006-06-02 15:53 ` Junio C Hamano [this message]
2006-06-02 16:03 ` Junio C Hamano
2006-06-02 16:04 ` Jeff King
2006-06-02 16:10 ` Junio C Hamano
2006-06-02 16:49 ` [PATCH] sha1_file: avoid re-preparing duplicate packs Jeff King
2006-06-02 17:47 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 15:56 [PATCH] handle concurrent pruning of packed objects Jeff King
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=7vwtbzblkf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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