From: "Dana How" <danahow@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Junio C Hamano" <junkio@cox.net>,
git@vger.kernel.org, danahow@gmail.com
Subject: Re: [PATCH] always start looking up objects in the last used pack first
Date: Sat, 2 Jun 2007 08:00:52 -0700 [thread overview]
Message-ID: <56b7f5510706020800o10541844t151cb82221d077d5@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.99.0705311015410.11491@xanadu.home>
On 5/31/07, Nicolas Pitre <nico@cam.org> wrote:
> Which makes me wonder about a possible incremental improvement to my
> patch: on failure to find an object in the last used pack, the search
> should then start again from the pack containing the commit from which
> this object search is related to. In the split pack case all commit
> objects will be located in the first pack so nothing will change there.
> In the multiple-fetch case then the search will always reset to packs
> not younger than the commit triggering those object lookups. Question
> is how to implement that nicely...
My immediate reaction to this patch was that there should be
a last-used-pack per object type. Or perhaps one for commits,
and one for trees+blobs [since the latter are intermingled]?
Unfortunately the interface only specifies
the SHA-1, not the object type, and certainly not the "commit
this is related to". I think your related-commit idea could be
very useful, but it does require some extra info to be passed
around which currently is not.
--
Dana L. How danahow@gmail.com +1 650 804 5991 cell
next prev parent reply other threads:[~2007-06-02 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 2:48 [PATCH] always start looking up objects in the last used pack first Nicolas Pitre
2007-05-31 3:24 ` Nicolas Pitre
2007-05-31 5:02 ` Shawn O. Pearce
2007-05-31 15:39 ` Nicolas Pitre
2007-06-02 15:00 ` Dana How [this message]
2007-06-02 14:53 ` Dana How
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=56b7f5510706020800o10541844t151cb82221d077d5@mail.gmail.com \
--to=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
--cc=spearce@spearce.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).