From: Jens Lehmann <Jens.Lehmann@web.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Jeff King" <peff@peff.net>, "Thomas Rast" <trast@inf.ethz.ch>,
git@vger.kernel.org, "Shawn Pearce" <spearce@spearce.org>,
"Jakub Narebski" <jnareb@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Pat Thoyts" <patthoyts@users.sourceforge.net>,
"Paul Mackerras" <paulus@samba.org>,
"Carlos Martín Nieto" <cmn@elego.de>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"David Michael Barr" <davidbarr@google.com>,
"Ramkumar Ramachandra" <artagnon@gmail.com>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Subject: Re: Google Summer of Code 2013 (GSoC13)
Date: Mon, 18 Feb 2013 21:02:01 +0100 [thread overview]
Message-ID: <512288B9.6010108@web.de> (raw)
In-Reply-To: <20130218193424.GC3234@elie.Belkin>
Am 18.02.2013 20:34, schrieb Jonathan Nieder:
> That said, I won't have time to mentor a project on my own. It takes
> a lot of time (or luck, to get the student that doesn't need
> mentoring).
That's my experience too. Also I think it really makes sense to have a
co-mentor so you can balance the load a bit.
> I'd be happy to help on a project with 1 or 2 co-mentors.
Same here.
next prev parent reply other threads:[~2013-02-18 20:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:23 Google Summer of Code 2013 (GSoC13) Thomas Rast
2013-02-18 17:42 ` Jeff King
2013-02-18 18:44 ` Ramkumar Ramachandra
2013-02-18 18:58 ` Jeff King
2013-02-18 19:45 ` Ramkumar Ramachandra
2013-02-18 19:57 ` Jonathan Nieder
2013-02-18 20:03 ` Thomas Rast
2013-02-19 7:51 ` Ramkumar Ramachandra
2013-02-18 21:13 ` Jeff King
2013-02-19 9:00 ` Ramkumar Ramachandra
2013-02-18 19:45 ` Thomas Rast
2013-02-18 20:01 ` Jens Lehmann
2013-02-18 22:32 ` Junio C Hamano
2013-02-19 7:08 ` Ramkumar Ramachandra
2013-02-19 7:25 ` Jonathan Nieder
2013-02-19 8:12 ` Ramkumar Ramachandra
2013-02-19 8:41 ` Thomas Rast
2013-02-19 16:29 ` Junio C Hamano
2013-02-19 16:39 ` Thomas Rast
2013-02-19 7:31 ` Junio C Hamano
2013-02-19 8:22 ` Ramkumar Ramachandra
2013-02-19 16:32 ` Junio C Hamano
2013-02-18 19:34 ` Jonathan Nieder
2013-02-18 20:02 ` Jens Lehmann [this message]
2013-02-20 6:17 ` Christian Couder
2013-02-18 20:44 ` Ramkumar Ramachandra
2013-02-18 21:07 ` Jeff King
2013-02-18 22:37 ` Junio C Hamano
2013-02-18 21:11 ` Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13)) Jonathan Nieder
2013-02-19 1:23 ` Duy Nguyen
2013-02-18 20:55 ` Google Summer of Code 2013 (GSoC13) Jeff King
2013-02-18 23:03 ` Jonathan Nieder
2013-02-20 6:50 ` Shawn Pearce
2013-02-20 12:07 ` Christian Couder
2013-02-20 12:26 ` Matthieu Moy
2013-02-21 15:41 ` Thomas Rast
2013-02-20 19:48 ` Michael Schubert
2013-02-21 14:29 ` Carlos Martín Nieto
2013-02-25 9:12 ` Florian Achleitner
2013-02-25 17:44 ` Junio C Hamano
2013-02-18 17:46 ` Thomas Rast
2013-02-18 18:02 ` Ronan Keryell
2013-02-18 19:48 ` Thomas Rast
2013-02-18 18:13 ` Ramkumar Ramachandra
2013-02-18 19:53 ` Thomas Rast
2013-02-19 1:17 ` Duy Nguyen
2013-02-26 4:59 ` Jaseem Abid
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=512288B9.6010108@web.de \
--to=jens.lehmann@web.de \
--cc=artagnon@gmail.com \
--cc=christian.couder@gmail.com \
--cc=cmn@elego.de \
--cc=davidbarr@google.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--cc=patthoyts@users.sourceforge.net \
--cc=paulus@samba.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=t.gummerer@gmail.com \
--cc=trast@inf.ethz.ch \
/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.