From: Martin Jambor <mjambor@suse.cz>
To: GCC Mailing List <gcc@gcc.gnu.org>,
Gfortran mailing list <fortran@gcc.gnu.org>,
libstdc++@gcc.gnu.org
Subject: Re: GCC GSoC 2022: Call for project ideas and mentors
Date: Wed, 12 Jan 2022 10:53:04 +0100 [thread overview]
Message-ID: <ri6sfttth4v.fsf@suse.cz> (raw)
In-Reply-To: <ri6czl4x2d9.fsf@suse.cz>
On Thu, Jan 06 2022, Martin Jambor wrote:
>
[...]
>
> I will update you as more details about GSoC 2022 become available.
>
The official timeline has been published at
https://developers.google.com/open-source/gsoc/timeline
I do not know how the "standard coding period" and "extended deadlines"
will exactly work, I suppose mentors and contributors will together
simply pick which one of the two to follow.
I intend to file our application around February 8th, so it would be
great to have our "selected ideas list" ready with all the details by
then.
Thanks,
Martin
next prev parent reply other threads:[~2022-01-12 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 16:20 Martin Jambor
2022-01-07 17:41 ` David Malcolm
2022-01-12 9:53 ` Martin Jambor [this message]
2022-01-12 10:01 ` Martin Jambor
2022-03-09 14:39 ` Martin Jambor
2022-03-10 2:09 ` Jerry D
2022-03-10 16:13 ` Damian Rouson
2022-03-10 16:22 ` 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=ri6sfttth4v.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).