git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Sarath Lakshman <sarathlakshman@slynux.com>
Cc: libgit2@librelist.org, git@vger.kernel.org, peff@peff.net,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: GSOC 11: Minimal git based client based on libgit2
Date: Sun, 3 Apr 2011 21:05:18 +0530	[thread overview]
Message-ID: <20110403153515.GB1480@kytes> (raw)
In-Reply-To: <AANLkTima7ezW+jFJKTKFmOvbibTkayaopF-NifKRQbp5@mail.gmail.com>

Hi Sarath,

Sarath Lakshman writes:
> I am an undergraduate student from India who wants to contribute to
> libgit2 during GSOC. I have worked with Fedora and Pardus during GSOC
> 2008, 2009 and 2010.

Thanks for writing.  Sorry about the late response.

> I am interested to work on libgit2 based minimal git client. I have
> built the libgit2 from source and tried to write basic git tasks. I
> have written a lot of python code in the past and now I look for
> writing good C code. Definitely, writing a git client based on libgit2
> seems interesting.

A lot of students are interested in this project.  Please browse
through the mailing list archives to see what the others have said --
Jonathan's response will probably be helpful [1].  Additionally,
please consider submitting more than one proposal to maximize your
changes.

Next steps: Post a concrete proposal to the list for feedback/
discussion.  You can make your application stronger by showing us some
code.

[1]: http://article.gmane.org/gmane.comp.version-control.git/170094

-- Ram

      reply	other threads:[~2011-04-03 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  5:06 GSOC 11: Minimal git based client based on libgit2 Sarath Lakshman
2011-04-03 15:35 ` Ramkumar Ramachandra [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

  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=20110403153515.GB1480@kytes \
    --to=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=libgit2@librelist.org \
    --cc=peff@peff.net \
    --cc=sarathlakshman@slynux.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).