From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Plato Kiorpelidis <kioplato@gmail.com>,
Shubham Mishra <shivam828787@gmail.com>,
Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>,
Labnan Khalid Masum <khalid.masum.92@gmail.com>,
Jayati Shrivastava <gaurijove@gmail.com>,
Jack McGuinness <jmcguinness2@ucmerced.edu>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: [GSoC] Contributor candidate introduction
Date: Mon, 18 Apr 2022 23:54:05 +0530 [thread overview]
Message-ID: <E6525E16-10E8-4C08-A596-6C16AD31F62A@gmail.com> (raw)
In-Reply-To: <660025e5-637d-8e93-e7ba-65a3ad474bad@gmail.com>
Adding other potential contributors to notify them too.
See mail with details below.
On 18 April 2022 11:24:34 pm IST, Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
>Hello all,
>
>Just a heads up that the proposal deadline (19Apr2022 18:00 UTC) is
>approaching shortly. I noticed that Abhradeep has submitted his proposal
>so far. Others, do make sure you submit your proposals in the GSoC
>website before the deadline. Only then can we consider your proposals
>for GSoC [ref].
>
>Thanks.
>
>[ref]:
>https://developers.google.com/open-source/gsoc/faq#should_i_send_proposals_directly_to_the_mentoring_organizations
>
>
--
Sivaraam
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2022-04-18 18:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 21:43 [GSoC] Contributor candidate introduction Plato Kiorpelidis
2022-04-05 21:59 ` Taylor Blau
2022-04-06 6:25 ` Christian Couder
2022-04-06 14:11 ` Shubham Mishra
2022-04-06 15:40 ` Taylor Blau
2022-04-06 15:43 ` Taylor Blau
2022-04-06 20:11 ` Kaartic Sivaraam
2022-04-07 7:16 ` Christian Couder
2022-04-07 9:25 ` Abhradeep Chakraborty
2022-04-08 20:34 ` Taylor Blau
2022-04-08 20:46 ` Junio C Hamano
2022-04-13 20:55 ` Taylor Blau
2022-04-15 21:01 ` Plato Kiorpelidis
2022-04-18 17:54 ` Kaartic Sivaraam
2022-04-18 18:06 ` Abhradeep Chakraborty
2022-04-19 4:38 ` Shubham Mishra
2022-04-19 15:54 ` Abhradeep Chakraborty
2022-04-18 18:24 ` Kaartic Sivaraam [this message]
2022-04-19 13:16 ` Jayati Shrivastava
2022-04-19 17:40 ` Kaartic Sivaraam
2022-04-20 13:16 ` Labnan Khalid Masum
2022-04-20 19:40 ` Kaartic Sivaraam
2022-04-21 8:58 ` Christian Couder
2022-04-18 18:33 ` Plato Kiorpelidis
2022-05-09 6:44 ` Kaartic Sivaraam
2022-05-09 15:12 ` Shubham Mishra
2022-05-09 16:36 ` Taylor Blau
2022-05-09 20:13 ` Plato Kiorpelidis
-- strict thread matches above, loose matches on Subject: below --
2022-04-05 21:30 Plato Kiorpelidis
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=E6525E16-10E8-4C08-A596-6C16AD31F62A@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=chakrabortyabhradeep79@gmail.com \
--cc=gaurijove@gmail.com \
--cc=git@vger.kernel.org \
--cc=jmcguinness2@ucmerced.edu \
--cc=khalid.masum.92@gmail.com \
--cc=kioplato@gmail.com \
--cc=me@ttaylorr.com \
--cc=shivam828787@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.