From: Kaartic Sivaraam <kaartic.sivaraam@gmail•com>
To: Patrick Steinhardt <ps@pks•im>, Jialuo She <shejialuo@gmail•com>
Cc: karthik nayak <karthik188@gmail•com>,
Christian Couder <christian.couder@gmail•com>,
shejialuo <shejialuo@gmail•com>,
Git Mailing List <git@vger•kernel.org>,
Junio C Hamano <gitster@pobox•com>
Subject: Re: Git in GSoC 2025
Date: Tue, 28 Jan 2025 23:50:57 +0530 [thread overview]
Message-ID: <ca0fcde5-72f7-4245-9536-c3b41bbde8a4@gmail.com> (raw)
In-Reply-To: <Z5c-jFA9OAT9x5s7@pks.im>
Hi Patrick and Jialuo,
On 27/01/25 13:36, Patrick Steinhardt wrote:
> On Mon, Jan 27, 2025 at 12:19:26PM +0530, Kaartic Sivaraam wrote:
>> While I have not included them as of yet, I wonder if the following ideas
>> which we
>> had last year[1] could still be retained this year:
>>
>> - Implement consistency checks for refs. The idea could be about
>> implementing further ref checks which Jialuo appears to be helping
>> out with. We could leave it if Jialuo prefers to continue working on
>> the same in a flow.
>
> The biggest omission right now is the reftable backend, but that one I
> plan to work on myself in this release cycle.
>
> I'll leave it to Jialuo to decide whether there's anything else in this
> context that would make for a good GSoC project, as he's been the
> primary driving force here.
>
Got it.
>> - Refactor git-bisect(1) to make its state self-contained
>
> I'd rather remove that project. It would be nice to have it, but it
> feels too risky for a GSoC project, and we have better ones.
>
Ok. I'll leave it dropped.
>> - Implement support for reftables in "dumb" HTTP transport
>
> I'd be fine mentoring this project.
>
Sure. I'll include this one. I've retained Karthik as a co-mentor.
Karthik, let me know in case of any concerns.
On 27/01/25 18:13, shejialuo wrote:
> One thing I could think about is to clean up "git-fsck(1)" to make the
> boundary between the ref checks and object checks clear which means we
> need to remove unnecessary checks and reorder the program sequence.
> However, I think this is a little risky for a GSoC project. So, I'd like
> to implement this later on my own.
Done. Thank you for your thoughts!
--
Sivaraam
next prev parent reply other threads:[~2025-01-28 18:21 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 [this message]
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
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=ca0fcde5-72f7-4245-9536-c3b41bbde8a4@gmail.com \
--to=kaartic.sivaraam@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=karthik188@gmail$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=shejialuo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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