From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: Heba Waly <heba.waly@gmail.com>, git <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Emily Shaffer <emilyshaffer@google.com>,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: GSoC and Outreachy Summer 2020?
Date: Fri, 21 Feb 2020 13:30:03 -0500 [thread overview]
Message-ID: <20200221183003.GA9786@coredump.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD1QbOK9g2oAhfTm2npoNF9Ay_HiAfFai9rJwZzc73cBbw@mail.gmail.com>
On Fri, Feb 21, 2020 at 05:03:47PM +0100, Christian Couder wrote:
> > I'd be happy to co-mentor an Outreachy intern with an experienced
> > mentor, hope I'm not too late.
>
> Thank you for your interest in co-mentoring! It's very much appreciated!
>
> I don't think you are late. It seems that February 25 at 4pm UTC is
> the deadline for project submission.
I think it is too late. That's the deadline for mentor project
submission, but the signup for orgs was Feb 18th.
-Peff
next prev parent reply other threads:[~2020-02-21 18:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 5:34 GSoC and Outreachy Summer 2020? Jeff King
2020-01-22 14:15 ` Johannes Schindelin
2020-02-04 11:55 ` Christian Couder
2020-02-04 16:11 ` Christian Couder
2020-02-04 16:13 ` Christian Couder
2020-02-04 16:37 ` Jeff King
2020-02-16 10:38 ` Christian Couder
2020-02-21 13:44 ` Heba Waly
2020-02-21 16:03 ` Christian Couder
2020-02-21 18:30 ` Jeff King [this message]
2020-02-22 7:20 ` Heba Waly
2020-02-23 21:44 ` Jeff King
2020-02-24 15:48 ` Johannes Schindelin
2020-02-25 20:20 ` Jeff King
2020-02-26 0:55 ` Heba Waly
2020-02-26 1:42 ` Jeff King
2020-02-26 10:17 ` Heba Waly
2020-02-26 18:38 ` Jeff King
2020-02-24 7:30 ` Christian Couder
2020-02-21 10:27 ` Christian Couder
2020-02-26 6:17 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200221183003.GA9786@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=heba.waly@gmail.com \
--cc=jonathantanmy@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).