git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: thisnukes4u@gmail.com
To: git@vger.kernel.org
Subject: Summer of Code - Cached Packs/Object Lists
Date: Sun, 22 Mar 2009 19:53:49 -0600 (MDT)	[thread overview]
Message-ID: <fsmi80et2dp57f5bdxUYAxe124vaj_firegpg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

Hey list,

     My name is Thomas Coppi, and I am a junior studying Computer Science at New Mexico Tech.  I've been using git for a few years now for managing coursework and personal projects, but have never looked much into the git source code or internals, so I figure that Summer of Code is a good way to get started.

     I am particularly interested in the packfile caching project mentioned on the wiki, but I have a couple of questions:

1.  Would it be possible to implement both the packfile and object list caching mechanisms, or might would one interfere with the other in some way?
2.  With just a quick perusal of the daemon source, I noticed that it shells out to the upload-pack command. Where would it be appropriate to implement such a caching mechanism, in the daemon proper, the upload-pack code, or would both need to be updated?

Thanks in advance, and sorry if my questions seem a little bit newbish, as I mentioned this is my first time diving into git internals.
-- 
Thomas Coppi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 271 bytes --]

             reply	other threads:[~2009-03-23  1:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23  1:53 thisnukes4u [this message]
2009-03-23  1:59 ` Summer of Code - Cached Packs/Object Lists Shawn O. Pearce
2009-03-23  2:49   ` Thomas Coppi
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=fsmi80et2dp57f5bdxUYAxe124vaj_firegpg@mail.gmail.com \
    --to=thisnukes4u@gmail.com \
    --cc=git@vger.kernel.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).