public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
Date: Thu, 29 Mar 2018 15:37:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1803291535050.25362@digraph.polyomino.org.uk> (raw)
In-Reply-To: <ri6d119xcu4.fsf@suse.cz>

Now the student application deadline has, I understand, passed, how do we 
go about collectively deciding which are the best proposals to request 
slots for?

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2018-03-29 15:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 17:54 Martin Jambor
2018-01-17 21:06 ` Joseph Myers
2018-01-19 13:17   ` Martin Jambor
2018-01-19 16:34     ` Joseph Myers
2018-01-19 17:31       ` Richard Biener
2018-01-17 22:16 ` Joel Sherrill
2018-01-18  9:19   ` Martin Liška
2018-01-19 13:50   ` Martin Jambor
2018-01-18  9:41 ` Martin Liška
2018-01-19 14:09   ` Martin Jambor
2018-01-19 14:13     ` Martin Jambor
2018-01-22 15:10       ` Martin Liška
2018-01-22 15:40     ` Martin Liška
2018-01-18 19:51 ` Eric Gallager
2018-01-18 20:31   ` Joseph Myers
2018-01-19 14:17     ` Martin Jambor
2018-01-18 23:10 ` Andi Kleen
2018-01-19 14:24   ` Martin Jambor
2018-01-23 10:56 ` Martin Jambor
2018-01-23 11:08   ` Prathamesh Kulkarni
2018-01-23 15:49     ` Martin Liška
2018-01-23 23:11     ` Martin Jambor
2018-02-13 13:02 ` Martin Jambor
2018-02-14 22:10   ` Janus Weil
2018-02-15  9:20     ` Martin Jambor
2018-02-15 10:52   ` Christopher Dimech
2018-02-15 12:12     ` Janus Weil
2018-02-15 13:59       ` Martin Jambor
2018-03-29 15:37   ` Joseph Myers [this message]
2018-03-29 16:40     ` Joseph Myers
2018-03-29 17:07     ` Martin Jambor
2018-04-03 11:30       ` Peryt, Sebastian
2018-04-03 14:09         ` Martin Jambor

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=alpine.DEB.2.20.1803291535050.25362@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).