git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vicent Martí" <tanoku@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>,
	Shawn Pearce <spearce@spearce.org>
Subject: Re: Git in GSoC 2014
Date: Wed, 26 Feb 2014 12:24:13 +0100	[thread overview]
Message-ID: <CAFFjANRqKqq_f9SCR4vP3YKUpfk1J2RQdB9G4gnY2OcZivzhXQ@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8Bw7JqokgGt46T7Xivk08F-DS4Dj-j1PWxoStu=cVzo5w@mail.gmail.com>

On Wed, Feb 26, 2014 at 12:16 PM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Tue, Feb 25, 2014 at 10:41 PM, Jeff King <peff@peff.net> wrote:
>> I'm pleased to announce that Git has been accepted to this year's Google
>> Summer of Code.
>>
>> Student proposals will start coming in on March 22. In the meantime
>> students will be reading our Ideas page[1] and enquiring about the
>> program on the mailing list and on irc. There are many ways that
>> existing git developers can help:
>>
>>   - continue to add to and polish the Ideas page
>
> One thing I noticed after tg/index-v4-format is both libgit2 and jgit
> do not seem to support index v4. So we could add "index v4 support on
> libgit2" to the idea page. It's a relatively small task though once
> you get a hang on index format.

That sounds like a nice task for the Summer of Code too, specially
with the current effort to make Index v4 more visible in Core Git.

I wonder if anybody from JGit would also be interested on mentoring
for the equivalent task (index v4 on JGit). I've CC'ed Shawn Pearce.

  reply	other threads:[~2014-02-26 11:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 15:41 Git in GSoC 2014 Jeff King
2014-02-25 16:42 ` Dmitry S. Dolzhenko
2014-02-25 17:15 ` Michael Haggerty
2014-02-26 10:23   ` Jeff King
2014-02-26 10:41     ` Michael Haggerty
2014-02-26 11:04       ` Jeff King
2014-02-26 11:25       ` Vicent Martí
2014-02-26 11:29         ` Jeff King
2014-02-26 19:48       ` Junio C Hamano
2014-02-27  7:34         ` Michael Haggerty
2014-02-27 19:19           ` Junio C Hamano
2014-02-27 20:26             ` Michael Haggerty
2014-02-27 20:32               ` Junio C Hamano
2014-04-22  1:06                 ` Andrew Ardill
2014-04-22  2:18                   ` Brian Gesiak
2014-02-26 11:16 ` Duy Nguyen
2014-02-26 11:24   ` Vicent Martí [this message]
2014-02-26 11:30     ` Jeff King
2014-02-26 16:48       ` Shawn Pearce
2014-02-26 17:15 ` Git in GSoC 2014 Suggestion: core.filemode always false for cygwin Torsten Bögershausen

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=CAFFjANRqKqq_f9SCR4vP3YKUpfk1J2RQdB9G4gnY2OcZivzhXQ@mail.gmail.com \
    --to=tanoku@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --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).