From: Christian Couder <chriscool@tuxfamily.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: GSoC 2010
Date: Fri, 12 Feb 2010 05:02:43 +0100 [thread overview]
Message-ID: <201002120502.43565.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20100211214833.GU9553@machine.or.cz>
Hi
Petr Baudis wrote:
> Hi!
>
> On Wed, Feb 10, 2010 at 09:23:55PM +0100, Sverre Rabbelier wrote:
> > Dscho created a GSoC 2010 idea's page [0] a few weeks ago, but it's a
> > bit sad at the moment (only two idea's). Part of the reason Git was
> > listed as 'example application' before was our awesome idea list, we
> > should live up to that again this year :). If you feel like mentoring
> > a summer of code student, or if you have a great idea, please add it
> > to the list so that our would-be students have some variety in
> > choosing their projects.
>
> Thanks for reminding me. :-) I have added giddy to the SoC project
> list, maybe someone will pick it up...
I added a "git sequencer again" proposal.
Regards,
Christian.
next prev parent reply other threads:[~2010-02-12 3:59 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 20:23 GSoC 2010 Sverre Rabbelier
2010-02-11 21:48 ` Petr Baudis
2010-02-12 4:02 ` Christian Couder [this message]
[not found] ` <e72faaa81002120222p19db9c75u737e2615c14930b1@mail.gmail.com>
[not found] ` <e72faaa81002120226y5e4b1c28tbaf6a7dccb9634dc@mail.gmail.com>
2010-02-12 10:56 ` web-based client for Git, was " Johannes Schindelin
2010-02-12 11:04 ` Pau Garcia i Quiles
2010-02-12 11:20 ` Johannes Schindelin
2010-02-12 11:35 ` Petr Baudis
[not found] ` <e72faaa81002120355t4c8596d0q66da4aeb4cce3a94@mail.gmail.com>
2010-02-12 11:58 ` Pavan Kumar Sunkara
2010-02-12 12:18 ` Petr Baudis
2010-02-12 12:24 ` Pavan Kumar Sunkara
2010-02-12 12:33 ` Petr Baudis
2010-02-12 12:44 ` Mike Hommey
2010-02-12 12:51 ` Petr Baudis
2010-02-12 12:54 ` Pavan Kumar Sunkara
2010-02-12 13:07 ` Johannes Schindelin
2010-02-12 13:05 ` Petr Baudis
2010-02-12 13:07 ` Pavan Kumar Sunkara
2010-02-12 13:15 ` Johannes Schindelin
2010-02-12 13:30 ` Jakub Narebski
2010-02-12 13:03 ` Mike Hommey
2010-02-12 18:24 ` david
2010-02-12 15:14 ` Scott Chacon
2010-02-12 16:45 ` Petr Baudis
2010-02-12 16:52 ` Jan Koprowski
2010-02-12 17:01 ` Pavan Kumar Sunkara
2010-02-12 8:06 ` Eric Wong
2010-02-12 9:02 ` Johannes Schindelin
2010-02-12 9:03 ` Sverre Rabbelier
2010-02-12 9:16 ` Mike Hommey
2010-02-12 9:35 ` Johannes Schindelin
2010-02-12 9:32 ` Sverre Rabbelier
2010-02-12 10:07 ` Mike Hommey
2010-02-12 10:49 ` strbuf & other stuff dual-licensing, was " Johannes Schindelin
2010-02-12 16:10 ` Daniel Barkalow
2010-02-12 16:41 ` Sverre Rabbelier
2010-02-12 19:16 ` Daniel Barkalow
2010-02-12 19:30 ` Sverre Rabbelier
2010-02-12 19:47 ` Scott Chacon
2010-02-12 9:34 ` Tay Ray Chuan
2010-02-12 9:52 ` Sverre Rabbelier
2010-02-12 9:30 ` Johannes Schindelin
2010-02-12 9:06 ` Sverre Rabbelier
2010-02-12 16:19 ` Daniel Barkalow
2010-02-12 16:43 ` Sverre Rabbelier
2010-02-14 6:52 ` Jeff King
2010-02-14 18:15 ` Johannes Schindelin
2010-02-15 8:30 ` Jeff King
2010-02-15 16:53 ` Shawn O. Pearce
2010-02-15 21:53 ` Sverre Rabbelier
2010-02-15 22:33 ` Johannes Schindelin
2010-02-15 22:31 ` Sverre Rabbelier
2010-02-15 22:36 ` Shawn O. Pearce
2010-02-15 22:58 ` Sverre Rabbelier
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=201002120502.43565.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=srabbelier@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.
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 NNTP newsgroup(s).