linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Evgeny Novikov <novikov@ispras.ru>,
	Alexey Khoroshilov <khoroshilov@ispras.ru>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	"lsb-discuss@lists.linux-foundation.org"
	<lsb-discuss@lists.linux-foundation.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Open Printing <printing-architecture@lists.linux-foundation.org>,
	chris holcombe <chris.holcombe@canonical.com>,
	Chris MacNaughton <chris.macnaughton@canonical.com>
Subject: Re: [lsb-discuss] Google Summer of Code 2016 - Many new applications
Date: Sat, 26 Mar 2016 11:25:32 -0300	[thread overview]
Message-ID: <56F69BDC.7050900@gmail.com> (raw)
In-Reply-To: <20160326141540.GA4104@kroah.com>

On 03/26/2016 11:15 AM, Greg KH wrote:
>> Which one?
>
> This one:
> 	https://summerofcode.withgoogle.com/dashboard/organization/6564234674569216/proposal/6320691074826240/
>
>> And are then all the other kernel-related applications to be ignored?
>
> I just went through them all again and left comments saying that they
> were not even a valid proposal, so yes, I don't see anything I can even
> consider for the kernel other than the above proposal.

Thank you very much. I have marked it with a star.

Can you look for a co-mentor and ask him for clicking "WANT TO MENTOR" 
on this, too?

Can you give me a list of all the other proposals which you considered 
not worthwhile (and where we do not need to wait for another mentor's 
opinion) so that I can mark them ignored?

    Till


  reply	other threads:[~2016-03-26 14:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 17:39 Google Summer of Code 2016 - Many new applications Till Kamppeter
2016-03-24 18:08 ` Greg KH
     [not found] ` <1943931458892174@web3o.yandex.ru>
2016-03-25 17:23   ` [lsb-discuss] " Greg KH
2016-03-25 22:58     ` Till Kamppeter
2016-03-25 23:46       ` Greg KH
2016-03-25 23:56   ` Till Kamppeter
2016-03-26  0:00     ` Till Kamppeter
2016-03-26  0:18       ` Greg KH
2016-03-26  0:39         ` Till Kamppeter
2016-03-26 14:15           ` Greg KH
2016-03-26 14:25             ` Till Kamppeter [this message]
2016-03-26 16:46               ` Greg KH
2016-03-26 17:04               ` Greg KH
2016-03-26 18:07                 ` Till Kamppeter
2016-03-28 14:42                   ` Greg KH
2016-03-30 18:33                     ` Till Kamppeter
2016-03-26 19:28       ` Denis Silakov
2016-03-26 19:43       ` Alexey Khoroshilov
2016-03-26 19:49         ` Luis R. Rodriguez
2016-03-26 20:00           ` Till Kamppeter
2016-03-26 19:59         ` Till Kamppeter
2016-03-26  0:17     ` Greg KH
2016-03-26  0:36       ` 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=56F69BDC.7050900@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=chris.holcombe@canonical.com \
    --cc=chris.macnaughton@canonical.com \
    --cc=greg@kroah.com \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --cc=mcgrof@gmail.com \
    --cc=novikov@ispras.ru \
    --cc=printing-architecture@lists.linux-foundation.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 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).