git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Yuxuan Shui <yshuiv7@gmail.com>
Cc: git@vger.kernel.org, tanoku@gmail.com
Subject: Re: GSoC proposal: port pack bitmap support to libgit2.
Date: Fri, 14 Mar 2014 00:34:04 -0400	[thread overview]
Message-ID: <20140314043404.GD31906@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGqt0zz1W1k92B+XRWEmMEv1=iyej+zi9QUCp2EhA=g+VnCt0g@mail.gmail.com>

On Wed, Mar 12, 2014 at 04:19:23PM +0800, Yuxuan Shui wrote:

> I'm Yuxuan Shui, a undergraduate student from China. I'm applying for
> GSoC 2014, and here is my proposal:
> 
> I found this idea on the ideas page, and did some research about it.
> The pack bitmap patchset add a new .bitmap file for every pack file
> which contains the reachability information of selected commits. This
> information is used to speed up git fetching and cloning, and produce
> a very convincing results.
> 
> The goal of my project is to port the pack bitmap implementation in
> core git to libgit2, so users of libgit2 could benefit from this
> optimization as well.
> 
> Please let me know if my proposal makes sense, thanks.

You'd want to flesh it out a bit more to show how you're thinking about
tackling the problem:

  - What are the areas of libgit2 that you will need to touch? Be
    specific. What's the current state of the packing code? What
    files and functions will you need to touch?

  - What are the challenges you expect to encounter in porting the code?

  - Can you give a detailed schedule of the summer's work? What will you
    work on in each week? What milestones do you expect to hit, and
    when?

-Peff

  parent reply	other threads:[~2014-03-14  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12  8:19 GSoC proposal: port pack bitmap support to libgit2 Yuxuan Shui
2014-03-13 17:20 ` Yuxuan Shui
2014-03-14  4:34 ` Jeff King [this message]
2014-03-20 13:38   ` Yuxuan Shui

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140314043404.GD31906@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=tanoku@gmail.com \
    --cc=yshuiv7@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).