From: "Shawn O. Pearce" <spearce@spearce.org>
To: P Baker <me@retrodict.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC] Google Summer of Code 2009 - new ideas
Date: Sat, 7 Mar 2009 12:55:47 -0800 [thread overview]
Message-ID: <20090307205547.GN16213@spearce.org> (raw)
In-Reply-To: <526944450903071159v3ddc92c5q9b3239f2aef97ac8@mail.gmail.com>
P Baker <me@retrodict.com> wrote:
> I posted to this list serve a few days ago about one of the 2008 SoC
> ideas. Are those ideas still plausible? Specifically, I'm interested
> in pursuing the git-submodule update. Is this off the drawing board?
Its not off the table just because of what someone else proposed
as an ideas list for 2009.
A GSoC project is what the student makes of it. You propose
something that you are interested in working on, that you think
you can complete in the time available within the program calendar,
and that the larger Git community would like to see implemented.
I think your post fell flat a few days ago with no replies because
it just didn't seem to invite any response from people. Remember,
we're all quite busy with our own projects and lives too, just
like you are, and we do Git hacking/emailing in our spare time.
An email needs to be somewhat compelling and invite a reply in
order to get a reply...
--
Shawn.
next prev parent reply other threads:[~2009-03-07 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 0:44 [GSoC] Google Summer of Code 2009 - new ideas Jakub Narebski
2009-03-07 1:09 ` Jan Janak
2009-03-07 2:56 ` Tay Ray Chuan
2009-03-08 23:59 ` Jakub Narebski
[not found] ` <20090309115026.obsvt34miowwcw8w@webmail.fussycoder.id.au>
2009-03-09 1:18 ` Jakub Narebski
2009-03-07 19:59 ` P Baker
2009-03-07 20:55 ` Shawn O. Pearce [this message]
2009-03-10 0:49 ` Shawn O. Pearce
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=20090307205547.GN16213@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=me@retrodict.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).