git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: tipecaml@gmail.com
Cc: git@vger.kernel.org
Subject: Re: GSoC 2011 : one more interested student.
Date: Mon, 04 Apr 2011 15:31:01 -0700	[thread overview]
Message-ID: <7vtyed7ioq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4D9912F8.60002@gmail.com> (Cyril Roelandt's message of "Mon, 04 Apr 2011 02:38:16 +0200")

Cyril Roelandt <tipecaml@gmail.com> writes:

> * Complete some libgit2 features
> Implementing a few key features seems like a great way to understand
> the way a VCS works. I would be interesting in working on the diff
> command and on the network related commands (git-push, git-fetch).
>
> * Build a minimal Git client based on libgit2
> It seems to be a quite popular task :) Hacking on this small git
> client would be a nice experience and would help me understanding how
> libgit2 works.

It seems that libgit2 project got GSoC slots out of the git project even
though they didn't apply themselves ;-)  But if you are interested in the
git project proper, there also are ideas on the wiki page.

> * Build in more external commands
> I am wondering why these commands should be rewritten. You know what
> they say : "if it is not broken, do not fix it" :-p Do these commands
> currently have performance issues ?

Performance won't be the primary issue; we would want to lose POSIX shell
and Perl dependency for Windows folks and that is the primary gain from
that part of the project.

  parent reply	other threads:[~2011-04-04 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  0:38 GSoC 2011 : one more interested student Cyril Roelandt
2011-04-04 12:05 ` Nguyen Thai Ngoc Duy
2011-04-04 15:57 ` Ramkumar Ramachandra
2011-04-04 18:11   ` Junio C Hamano
2011-04-04 22:31 ` Junio C Hamano [this message]
2011-04-07  0:53   ` Jeff King

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=7vtyed7ioq.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=tipecaml@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).