From: Derrick Stolee <derrickstolee@github.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Git Community <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
Emily Shaffer <emilyshaffer@google.com>,
Atharva Raykar <raykar.ath@gmail.com>,
ZheNing Hu <adlternative@gmail.com>,
Derrick Stolee <stolee@gmail.com>, Victoria Dye <vdye@github.com>,
Hariom verma <hariom18599@gmail.com>,
Philip Oakley <philipoakley@iee.email>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: Git in GSoC 2022?
Date: Mon, 7 Mar 2022 14:50:53 -0500 [thread overview]
Message-ID: <e1b59df0-2ec2-2854-7c53-b1a57bd157c3@github.com> (raw)
In-Reply-To: <CA+ARAtquQOtcDtc0nCWkxyP2enb_QbxyoK9b3HWf-2JzbaKbkQ@mail.gmail.com>
On 3/7/2022 2:38 PM, Kaartic Sivaraam wrote:
> Hi all,
>
> I'm glad to share the news that Git has been accepted as a mentoring
> organization [1] for GSoC!
Excellent news! Thanks for all your hard work on the application.
> Since it is possible to invite mentors now, I've invited the mentors who
> have suggested ideas[2] so far. I've used the e-mail mentioned in the
> ideas page to send the invite.
I've submitted the form for mine. Thanks!
-Stolee
next prev parent reply other threads:[~2022-03-07 19:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 18:29 Git in GSoC 2022? Kaartic Sivaraam
2022-01-26 20:05 ` Taylor Blau
2022-01-27 9:32 ` Christian Couder
2022-01-29 18:09 ` Kaartic Sivaraam
2022-02-13 13:35 ` Christian Couder
2022-02-15 20:34 ` Kaartic Sivaraam
2022-02-15 23:18 ` Hariom verma
2022-02-16 15:40 ` Christian Couder
2022-02-17 15:07 ` Hariom verma
2022-02-17 17:18 ` Kaartic Sivaraam
2022-02-18 2:14 ` Hariom verma
2022-02-26 20:29 ` Kaartic Sivaraam
2022-02-28 11:03 ` Christian Couder
2022-02-28 18:02 ` Kaartic Sivaraam
2022-03-01 13:51 ` Christian Couder
2022-03-04 18:34 ` Kaartic Sivaraam
2022-01-27 3:55 ` Bagas Sanjaya
2022-01-27 9:44 ` Christian Couder
[not found] ` <nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet>
2022-01-29 18:36 ` Kaartic Sivaraam
2022-03-09 11:49 ` Johannes Schindelin
2022-03-09 19:57 ` Kaartic Sivaraam
2022-01-27 14:39 ` Derrick Stolee
2022-01-29 18:19 ` Kaartic Sivaraam
2022-02-02 17:42 ` Derrick Stolee
2022-01-27 15:00 ` ZheNing Hu
2022-01-29 17:43 ` Kaartic Sivaraam
2022-02-03 14:12 ` Philip Oakley
2022-02-12 18:12 ` Kaartic Sivaraam
2022-02-13 9:33 ` Christian Couder
2022-02-15 15:05 ` Philip Oakley
2022-02-15 20:32 ` Kaartic Sivaraam
2022-02-16 15:55 ` Christian Couder
2022-02-17 17:28 ` Kaartic Sivaraam
2022-03-07 19:38 ` Kaartic Sivaraam
2022-03-07 19:50 ` Derrick Stolee [this message]
2022-03-07 22:25 ` Hariom verma
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=e1b59df0-2ec2-2854-7c53-b1a57bd157c3@github.com \
--to=derrickstolee@github.com \
--cc=adlternative@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hariom18599@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.com \
--cc=philipoakley@iee.email \
--cc=raykar.ath@gmail.com \
--cc=stolee@gmail.com \
--cc=vdye@github.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).