From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>, git <git@vger.kernel.org>,
Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
Victoria Dye <vdye@github.com>,
Karthik Nayak <karthik.188@gmail.com>
Subject: Re: Git in GSoC 2024
Date: Tue, 6 Feb 2024 00:09:55 +0530 [thread overview]
Message-ID: <26cf6320-7ead-4ca0-b4b8-ca7008cae401@gmail.com> (raw)
In-Reply-To: <CAP8UFD3GBT7s1jGOc=fe6XdYGF1c--tMBDiy_sDg1Afsa=drDw@mail.gmail.com>
Hi Christian,
On 05/02/24 22:37, Christian Couder wrote:
> Hi Kaartic, Patrick, Karthik and all,
>
> Thanks for creating the page!
>
> I have just applied the patch Patrick sent to the mailing list with
> the ideas related to reftable.
>
Thank you! I've now successfully submitted the application for Git using
the Ideas page we have :-)
Let's hope that we get selected this year. We should know about that by
February 21 - 18:00 UTC.
> Yeah, we need a decent idea page, but it doesn't need to be finalized.
> I think we can still make changes after the deadline (which is for the
> Open Source Orgs to apply).
>
Indeed. Let's see if we could get any new ideas / potential mentors for
this GSoC :-]
>> Christian,
>>
>> It would be great if you could look into and improve the detail for the
>> unit test migration idea. I just added a very terse description based on
>> what I could get my hands on. If you think the description we used for
>> the Outreachy round would do, kindly update the page with the same or
>> kindly share it here so that I could update the same in the ideas page :-)
>
> The project description for Outreachy was not very elaborate and is
> now quite outdated. I have instead improved the project description in
> the Ideas page.
>
That's great. Thanks!
--
Sivaraam
next prev parent reply other threads:[~2024-02-05 18:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:16 Git in GSoC 2024 Kaartic Sivaraam
2024-01-30 8:38 ` Christian Couder
2024-01-30 9:08 ` Patrick Steinhardt
2024-01-31 13:10 ` Patrick Steinhardt
2024-01-31 17:57 ` Kaartic Sivaraam
2024-01-31 18:03 ` Kaartic Sivaraam
2024-02-01 9:00 ` Karthik Nayak
2024-02-01 9:38 ` Patrick Steinhardt
2024-02-03 11:41 ` Kaartic Sivaraam
2024-02-04 14:29 ` Kaartic Sivaraam
2024-02-05 8:39 ` [PATCH] Add ideas for " Patrick Steinhardt
2024-02-05 16:43 ` Christian Couder
2024-02-05 18:55 ` Kaartic Sivaraam
2024-02-06 5:51 ` Patrick Steinhardt
2024-02-06 8:13 ` Christian Couder
2024-02-08 14:02 ` Kaartic Sivaraam
2024-02-09 6:27 ` Patrick Steinhardt
2024-02-09 8:36 ` Christian Couder
2024-02-06 5:47 ` Patrick Steinhardt
2024-02-06 8:26 ` Christian Couder
2024-02-05 17:07 ` Git in " Christian Couder
2024-02-05 18:39 ` Kaartic Sivaraam [this message]
2024-02-21 5:02 ` Kaartic Sivaraam
2024-02-21 6:19 ` Patrick Steinhardt
2024-02-21 8:43 ` Christian Couder
2024-02-21 8:59 ` Karthik Nayak
2024-02-22 4:31 ` Kaartic Sivaraam
2024-02-22 7:49 ` Patrick Steinhardt
2024-02-22 8:57 ` Karthik Nayak
2024-02-22 12:02 ` Christian Couder
2024-02-22 14:05 ` Kaartic Sivaraam
2024-02-22 15:52 ` Patrick Steinhardt
2024-02-24 17:34 ` Kaartic Sivaraam
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=26cf6320-7ead-4ca0-b4b8-ca7008cae401@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
--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.
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).