public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: PRANIL DEY <mkdeyp@gmail.com>, gcc@gcc.gnu.org
Cc: hubicka@ucw.cz
Subject: Re: GSoC "Nothrow detection" proposal review
Date: Fri, 12 Apr 2024 13:07:23 +0200	[thread overview]
Message-ID: <ri634rqltzo.fsf@virgil.suse.cz> (raw)
In-Reply-To: <CABy-c6yPYBLzmeH08XqYXHDww9BeXMrTeMG_r9SB=FHOYysJmA@mail.gmail.com>

Hello,

On Fri, Apr 05 2024, PRANIL DEY wrote:
> Hello GCC Community,
> I am Pranil Dey and I had submitted a proposal for the project "Improve
> nothrow detection in GCC", but as the deadline period was a holiday time I
> wanted to ask you to review my proposal now.
> I am already getting familiar with the code but I wanted some pointers for
> now till selection time so as to read up some more and work more
> efficiently if selected.
> Proposal link -
> https://drive.google.com/file/d/1GynfephYrwaOHG4l7al3dNedrnjL9Dsr/view?usp=drive_link

I can assure you that we are diligently evaluating all GSoC proposals
including yours (I can also confirm I can see your proposal my GSoC Org
Admin dahsboard) and will finish doing so by the deadline set by Google.

Google reserves the right to announce the acceptance themselves - and
they have they final say when they determine the number of slots an
organization receives, therefore we cannot publicly disclose much
details about the evaluation process, I am afraid.

Martin

      reply	other threads:[~2024-04-12 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 16:58 PRANIL DEY
2024-04-12 11:07 ` Martin Jambor [this message]

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=ri634rqltzo.fsf@virgil.suse.cz \
    --to=mjambor@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mkdeyp@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 read-only IMAP folder(s) and NNTP newsgroup(s).