git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Peter Eriksen" <s022018@student.dtu.dk>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Summer of Code 2008 project application draft: Pack v4
Date: Mon, 31 Mar 2008 13:06:48 +0200	[thread overview]
Message-ID: <20080331110648.GA26579@bohr.gbar.dtu.dk> (raw)
In-Reply-To: <20080331041217.GE10274@spearce.org>

On Mon, Mar 31, 2008 at 12:12:17AM -0400, Shawn O. Pearce wrote:
> Peter Eriksen <s022018@student.dtu.dk> wrote:
> > Here is a draft of my application for the Google Summer of Code 2008.
> ...
> > The project goal is to rebase the code and ideas developed for the
> > version 4 of the git pack format, which showed good promise of making
> > packs smaller, and faster.
> 
> Have you had a chance to look at those patches yet?

Yes, more than a year ago, see e.g. 
http://thread.gmane.org/gmane.comp.version-control.git/43016
but I will need to refresh my memory.

> Or the code that they touch, but which has been heavily modified
> since then (like say builtin-pack-objects.c)?

No, I am not yet too familiar with all the newest changes. I obviously
would need to read that code carefully.

> I would hope that forward-porting those patches would only take
> us through to about the mid-term, and then finishing out the bulk
> of the series (like commit dict encoding, maybe dict of object ids
> used in trees) would be the remainder of the summer.  But that may
> be aggressive.

I will think a bit about this, and try to make a time line.

> To be successful I think the student working on
> this project needs to spend some time during the bonding period to
> understand the current pack v2 format and how the pack v4 format
> was going to address some of the shortcomings of v2.

Yes, since I basic understanding of the pack formats some time ago, it
should be possible to get up to speed fairly quickly in the bonding
period.

> To some extent I have left the design details about pack v4 off
> the ideas page hoping to draw students into explaining their own
> ideas for how to improve upon Git's pack data storage.

This would be nice of course, but my time is quite limited at the
moment, so this will not be possible for me yet. The reason why I
would like to participate this year is because my summer vacation this
year will be much earlier, and will fit very well into the GSoC window.

Thank you for comments.

Peter

      reply	other threads:[~2008-03-31 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 20:50 Summer of Code 2008 project application draft: Pack v4 Peter Eriksen
2008-03-31  4:12 ` Shawn O. Pearce
2008-03-31 11:06   ` Peter Eriksen [this message]

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=20080331110648.GA26579@bohr.gbar.dtu.dk \
    --to=s022018@student.dtu.dk \
    --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).