From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Siddharth Asthana <siddharthasthana31@gmail.com>
Cc: Git at SFC <git@sfconservancy.org>,
Pablo <pabloosabaterr@gmail.com>,
Usman Akinyemi <usmanakinyemi202@gmail.com>,
Tian Yuchen <cat@malon.dev>, git <git@vger.kernel.org>,
Christian Couder <christian.couder@gmail.com>
Subject: Re: Participating in Outreachy's December 2026 cohort
Date: Mon, 14 Sep 2026 13:54:44 +0530 [thread overview]
Message-ID: <f2c1a858-e259-4e9f-a48f-f553f4d43153@gmail.com> (raw)
In-Reply-To: <080f0485-3cf7-481a-8c39-c69afc81fbd8@gmail.com>
Hi Siddarth,
On 9/14/26 12:08, Siddharth Asthana wrote:
>>
>> The links to these projects are currently only available to approved
>> mentors and coordinators. I applied to mentor both of these projects
>> as this was required to submit the projects, but I am very much
>> willing to remove myself from mentoring one of these projects.
>>
>> So please apply to (co-)mentor one of these projects, or submit other
>> projects you are willing to mentor if you prefer.
>
>
> Applied as co-mentor on the parse-options / early-scan one.
>
Thank you for volunteering! I've approved you as a mentor for that project.
--
Sivaraam
next prev parent reply other threads:[~2026-09-14 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 10:55 Participating in Outreachy's December 2026 cohort Christian Couder
2026-08-26 11:39 ` Usman Akinyemi
2026-09-02 13:20 ` Kaartic Sivaraam
2026-09-03 10:24 ` Pablo Sabater
2026-09-05 8:26 ` Christian Couder
2026-09-09 9:12 ` Christian Couder
2026-09-14 6:38 ` Siddharth Asthana
2026-09-14 8:24 ` Kaartic Sivaraam [this message]
2026-09-14 8:37 ` Pablo Sabater
2026-09-14 9:41 ` Kaartic Sivaraam
2026-09-16 20:58 ` Christian Couder
2026-09-17 11:07 ` Kaartic Sivaraam
2026-09-19 13:43 ` Christian Couder
2026-10-05 18:19 ` Pablo Sabater
2026-10-08 13:20 ` Kaartic Sivaraam
2026-10-08 14:05 ` Usman Akinyemi
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=f2c1a858-e259-4e9f-a48f-f553f4d43153@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=cat@malon.dev \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=pabloosabaterr@gmail.com \
--cc=siddharthasthana31@gmail.com \
--cc=usmanakinyemi202@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