From: Cyril Roelandt <tipecaml@gmail.com>
To: git@vger.kernel.org
Subject: GSoC 2011 : one more interested student.
Date: Mon, 04 Apr 2011 02:38:16 +0200 [thread overview]
Message-ID: <4D9912F8.60002@gmail.com> (raw)
Hi.
I am currently studying Computer Science and Engineering. I have been
using Open Source software for quite a while now, but I have not
contributed a lot of code to Open Source projects - except for a few
patches to Gnome.
Being a git user, I would be interested in working on this project. I
believe that taking part in the GSoC would be a good opportunity for me
to discover the guts of a version control system.
* 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.
* 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 ?
I will be working in a research lab until the end of June, but I will
have more free time in July/August, that I could use to hack on git,
which means I may have less time than most US students, who can enjoy a
slightly longer summer break. Do you think it would be possible to work
one of these projects anyway ?
Best regards,
Cyril.
next reply other threads:[~2011-04-04 0:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 0:38 Cyril Roelandt [this message]
2011-04-04 12:05 ` GSoC 2011 : one more interested student 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
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=4D9912F8.60002@gmail.com \
--to=tipecaml@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).