From: Andreas Ericsson <ae@op5.se>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Google Summer of Code 2009
Date: Mon, 12 Jan 2009 12:16:32 +0100 [thread overview]
Message-ID: <496B2690.2010902@op5.se> (raw)
In-Reply-To: <20090107183033.GB10790@spearce.org>
Just chiming in that I can probably help mentoring whoever goes
with libgit2. I do not have enough spare time for me to promise
that I can be there as much as I think is necessary and proper,
but I'll gladly help out.
On a side-note, I think all mentors should urge the students in
the strongest possible terms to deliver their work to git@vger
as soon as possible. From previous years experience, successful
projects are those that the list sees code from within a week
or two after the project's started, while the projects that are
kept in the dark rarely (if ever?) finish successfully.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2009-01-12 11:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 18:30 Google Summer of Code 2009 Shawn O. Pearce
2009-01-07 23:11 ` Miklos Vajna
2009-01-07 23:12 ` Alex Riesen
2009-01-07 23:14 ` Shawn O. Pearce
2009-01-07 23:30 ` Johannes Schindelin
2009-01-07 23:40 ` Alex Riesen
2009-01-08 7:55 ` Sam Vilain
2009-01-10 19:33 ` Jakub Narebski
2009-01-10 19:58 ` Johannes Schindelin
2009-01-12 13:01 ` Christian Couder
2009-01-14 22:01 ` Stephan Beyer
2009-01-12 11:16 ` Andreas Ericsson [this message]
2009-01-12 13:20 ` Christian Couder
2009-01-12 15:35 ` Shawn O. Pearce
2009-01-12 13:25 ` Johannes Schindelin
2009-01-12 15:33 ` Shawn O. Pearce
2009-01-12 17:23 ` Johannes Schindelin
2009-01-12 17:48 ` Shawn O. Pearce
2009-01-12 15:37 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2009-03-21 9:41 Yoshinori K. Okuji
2009-03-21 16:26 ` Bean
2009-03-21 19:54 ` Vesa Jääskeläinen
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=496B2690.2010902@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.