From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Till Kamppeter <till.kamppeter@gmail.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Witold Sowa <witold.sowa@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: Google Summer of Code 2010 - Please resolve duplicates
Date: Mon, 19 Apr 2010 23:58:35 +0100 [thread overview]
Message-ID: <m2v3ace41891004191558k2ade8cdic258601bd1059a8f@mail.gmail.com> (raw)
In-Reply-To: <20100419224634.GG1800@kroah.com>
On Mon, Apr 19, 2010 at 11:46 PM, Greg KH <greg@kroah.com> wrote:
<snipped>
>> I have opened the duplicate information for students to all of your
>> orgs. If you view your student proposals now the ones that are ranked
>> to be accepted that are duplicated with another org will be marked in
>> red. If you click on the proposal you will see the contact information
>> for the other organization(s)'s admins near the bottom of the
>> proposal.
<snipped>
> Have a pointer to the web site to do this?
I think the idea from the original announcement is for each pair of
organizations with duplicate applications, to contact each other, for
one of the organization to drop the student's application so the other
one can proceed. e.g. if a student applies to both linux foundation
and gnome (for example), the linux foundation admin should contact the
gnome admin to decide which organization to take the student (and
which one to withdraw. As for the question itself, somewhere under:
- http://socghop.appspot.com/gsoc/program/home/google/gsoc2010
next prev parent reply other threads:[~2010-04-19 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 19:39 Google Summer of Code 2010 - Please resolve duplicates Till Kamppeter
2010-04-19 22:46 ` Greg KH
2010-04-19 22:57 ` Till Kamppeter
2010-04-20 7:19 ` Till Kamppeter
2010-04-19 22:58 ` Hin-Tak Leung [this message]
2010-04-20 6:13 ` Johannes Berg
2010-04-20 12:43 ` Grant Likely
2010-04-20 17:31 ` Till Kamppeter
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=m2v3ace41891004191558k2ade8cdic258601bd1059a8f@mail.gmail.com \
--to=hintak.leung@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=till.kamppeter@gmail.com \
--cc=tytso@mit.edu \
--cc=witold.sowa@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).