git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: karthik nayak <karthik.188@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git <git@vger.kernel.org>
Cc: pyokagan@gmail.com, Jeff King <peff@peff.net>,
	Christian Couder <christian.couder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Stefan Beller <sbeller@google.com>
Subject: Re: GSoC 2015: 2 accepted proposals
Date: Tue, 28 Apr 2015 17:47:20 +0530	[thread overview]
Message-ID: <553F7A50.1080907@gmail.com> (raw)
In-Reply-To: <vpqoam9mjuo.fsf@anie.imag.fr>

Hello to Everyone,

On 04/28/2015 01:20 AM, Matthieu Moy wrote:
> Hi,
>
> The results just got offical: the Git organization has 2 students
> accepted for the summer of code 2015.
>
> Karthik Nayak will work on "Unifying git branch -l, git tag -l, and git
> for-each-ref" mentored by Christian Couder and yours truly.

Thanks a lot for accepting my proposal and giving me an opportunity to 
work with Git via GSoC. Can't express how excited I am.

As Matthieu mentioned I will be working on "Unifying git branch -l, git 
tag -l, and git for-each-ref". I plan to start off by going through the 
existing implementation of each of the above commands and come up with a 
design for unification for now. Also to take notes from Jeff King's 
attempt at unification[1].

I will be pushing all my work to my personal Git repository on Github[2].
Where anyone can get involved. Will also make sure to notify the mailing 
list on a regular basis on what is going on with my project.

Looking forward to work with Git and complete this project successfully.

Regards,
Karthik

>
> Paul Tan will work on "Make git-pull and git-am builtins", mentored by
> Johannes Schindelin and Stefan Beller.

Congrats Paul, I wish you the very best.

>
> Regards,
>

[1] https://github.com/peff/git/tree/jk/for-each-ref-contains-wip
[2] https://github.com/KarthikNayak/git

      parent reply	other threads:[~2015-04-28 12:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 19:50 GSoC 2015: 2 accepted proposals Matthieu Moy
2015-04-28  8:58 ` Paul Tan
2015-04-29 15:27   ` Johannes Schindelin
2015-05-06  0:00   ` [PATCH 0/6] Make pull a builtin Stephen Robin
2015-05-06  0:00     ` [PATCH 1/6] merge: tidy up options Stephen Robin
2015-05-06  0:00     ` [PATCH 2/6] merge: move error message given when a merge needs committing to advice.c Stephen Robin
2015-05-06  0:00     ` [PATCH 3/6] merge-base: split handle_fork_point to make reuse easier Stephen Robin
2015-05-06  0:00     ` [PATCH 4/6] pull: reimplement as a builtin in C Stephen Robin
2015-05-06  0:00     ` [PATCH 5/6] pull: allow interactive rebase Stephen Robin
2015-05-06  5:43       ` Johannes Schindelin
2015-05-06  0:00     ` [PATCH 6/6] parse-remote: dismantle git-parse-remote.sh Stephen Robin
2015-05-06  4:27     ` [PATCH 0/6] Make pull a builtin Paul Tan
2015-04-28 12:17 ` karthik nayak [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=553F7A50.1080907@gmail.com \
    --to=karthik.188@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=pyokagan@gmail.com \
    --cc=sbeller@google.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.
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).