git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Yuxuan Shui <yshuiv7@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: GSoC proposal: port pack bitmap support to libgit2.
Date: Fri, 14 Mar 2014 01:20:58 +0800	[thread overview]
Message-ID: <CAGqt0zy=av=V--REMz2Q1VRZW9mU5Ng=NN=TAAZiUbzskUZbgQ@mail.gmail.com> (raw)
In-Reply-To: <CAGqt0zz1W1k92B+XRWEmMEv1=iyej+zi9QUCp2EhA=g+VnCt0g@mail.gmail.com>

Hi,

On Wed, Mar 12, 2014 at 4:19 PM, Yuxuan Shui <yshuiv7@gmail.com> wrote:
> Hi,
>
> 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.
>
> P.S. I've submitted by microproject patch[1], but haven't received any
> response yet.
>
> [1]: http://thread.gmane.org/gmane.comp.version-control.git/243854
>
> --
> Regards
> Yuxuan Shui

Could anyone please review my proposal a little bit? Is this project
helpful and worth doing? Did I get anything wrong in my proposal?

Thanks.

-- 

Regards
Yuxuan Shui

  reply	other threads:[~2014-03-13 17:21 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 [this message]
2014-03-14  4:34 ` Jeff King
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='CAGqt0zy=av=V--REMz2Q1VRZW9mU5Ng=NN=TAAZiUbzskUZbgQ@mail.gmail.com' \
    --to=yshuiv7@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. 
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).