From: Thomas Coppi <thisnukes4u@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Summer of Code - Cached Packs/Object Lists
Date: Sun, 22 Mar 2009 20:49:57 -0600 (MDT) [thread overview]
Message-ID: <fsmk86y8vqj4f56b08UYAxe124vaj_firegpg@mail.gmail.com> (raw)
In-Reply-To: <20090323015936.GM23521@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Sun, Mar 22, 2009 at 7:59 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Please line wrap your email at something useful to others when
> quoting, like 70-72 characters per line.
Sorry about that.
> You could do both. But I think most people on the list will argue
> that doing both is overkill and only one is necessary, and further,
> that only the one that offers the "biggest bank for the buck"
> should be implemented.
Alright, that seems reasonable. Given that I think I would lean
towards implementing an object list caching mechanism, since that seems
to be more generally applicable. The logic for this would then need to
be in the rev-list code(as mentioned in the JGit discussion), correct?
Oh, and I forgot to mention in my previous email that I am also
available on freenode IRC under the nick tcoppi.
Thanks again,
--
Thomas Coppi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 271 bytes --]
next prev parent reply other threads:[~2009-03-23 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 1:53 Summer of Code - Cached Packs/Object Lists thisnukes4u
2009-03-23 1:59 ` Shawn O. Pearce
2009-03-23 2:49 ` Thomas Coppi [this message]
2009-03-23 2:52 ` Shawn O. Pearce
2009-03-23 14:41 ` Nicolas Pitre
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=fsmk86y8vqj4f56b08UYAxe124vaj_firegpg@mail.gmail.com \
--to=thisnukes4u@gmail.com \
--cc=git@vger.kernel.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).