From: shejialuo <shejialuo@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
Ghanshyam Thakkar <shyamthakkar001@gmail.com>,
Karthik Nayak <karthik.188@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git in GSoC 2025
Date: Fri, 28 Feb 2025 13:06:48 +0800 [thread overview]
Message-ID: <Z8FEaIzK60EDMEFn@ArchLinux> (raw)
In-Reply-To: <6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com>
On Fri, Feb 28, 2025 at 08:33:38AM +0530, Kaartic Sivaraam wrote:
> Hi Christian, Patrick, Ghanshyam, Karthik, Jialuo and all,
>
>
> On 19 January 2025 3:43:29 pm IST, Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
> >Hello everyone,
> >
> >It is that time of year. GSoC Org Applications for 2025 are open now[1].
> >They are due before Tuesday, February 11 at 1800 UTC. It's good to see that few contributors have already started working on microprojects this year :-)
> >
>
> I'm glad to announce that we've successfully been selected as a mentoring organization for GSoC this year[1]!
>
Thanks for working on this.
> Christian, Patrick and Karthik,
>
> As you're already members of the organization kindly log in to the GSoC portal to read and accept this year's Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.
>
> Ghanshyam and Jialuo,
>
> As you're new to the program, I've sent you an invite. You should've got an e-mail about it. Kindly sign up via the same to read an accept the Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.
>
I have already signed up and accepted the agreement.
> Let's look forward towards for a great summer this year! :-)
>
Yes, that would be a great journey.
Thanks,
Jialuo
next prev parent reply other threads:[~2025-02-28 5:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 10:13 Git in GSoC 2025 Kaartic Sivaraam
2025-01-20 7:07 ` Patrick Steinhardt
2025-01-20 13:38 ` shejialuo
2025-01-21 11:47 ` Oswald Buddenhagen
[not found] ` <CA+ARAtqfXo75PzzB3cQjDbvLxwytUK=xJiGG=VHZ1sNCcfyktQ@mail.gmail.com>
2025-01-27 8:06 ` Patrick Steinhardt
2025-01-27 12:43 ` shejialuo
2025-01-28 18:20 ` Kaartic Sivaraam
2025-01-28 17:30 ` Kaartic Sivaraam
2025-02-02 11:52 ` Kaartic Sivaraam
2025-02-03 8:45 ` Patrick Steinhardt
2025-02-03 11:53 ` Karthik Nayak
2025-02-04 2:29 ` shejialuo
2025-02-04 18:33 ` Kaartic Sivaraam
2025-02-05 13:20 ` Christian Couder
2025-02-07 7:32 ` Kaartic Sivaraam
2025-02-07 8:07 ` Christian Couder
2025-02-07 10:55 ` Patrick Steinhardt
2025-02-11 5:18 ` Kaartic Sivaraam
2025-02-16 12:56 ` Ghanshyam Thakkar
2025-02-16 13:53 ` Kaartic Sivaraam
2025-02-16 17:48 ` Junio C Hamano
2025-02-17 15:21 ` Ghanshyam Thakkar
2025-03-07 10:01 ` Karthik Nayak
2025-03-20 17:50 ` Kaartic Sivaraam
2025-03-21 21:02 ` Karthik Nayak
2025-02-08 15:34 ` shejialuo
2025-02-10 17:00 ` Karthik Nayak
2025-01-20 8:19 ` Christian Couder
2025-01-20 11:09 ` Patrick Steinhardt
2025-01-21 20:35 ` Junio C Hamano
2025-01-30 5:44 ` Kaartic Sivaraam
2025-01-30 7:32 ` Patrick Steinhardt
2025-01-30 8:37 ` Christian Couder
2025-01-30 10:56 ` Patrick Steinhardt
2025-01-30 19:18 ` Junio C Hamano
2025-01-30 21:00 ` Junio C Hamano
2025-01-31 4:51 ` Patrick Steinhardt
2025-01-31 16:09 ` Junio C Hamano
2025-02-03 8:49 ` Patrick Steinhardt
2025-01-31 4:48 ` Patrick Steinhardt
2025-02-03 13:21 ` Junio C Hamano
2025-02-04 18:36 ` Kaartic Sivaraam
2025-01-30 5:39 ` Kaartic Sivaraam
2025-01-20 10:12 ` Karthik Nayak
2025-01-20 13:27 ` shejialuo
2025-02-28 3:03 ` Kaartic Sivaraam
2025-02-28 5:06 ` shejialuo [this message]
2025-02-28 6:16 ` Patrick Steinhardt
2025-02-28 7:56 ` Christian Couder
2025-02-28 10:12 ` Ghanshyam Thakkar
2025-03-01 0:47 ` Kaartic Sivaraam
2025-03-03 10:00 ` Karthik Nayak
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=Z8FEaIzK60EDMEFn@ArchLinux \
--to=shejialuo@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
--cc=shyamthakkar001@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 NNTP newsgroup(s).