From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
Patrick Steinhardt <ps@pks.im>
Cc: 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: [PATCH] Add ideas for GSoC 2024
Date: Tue, 6 Feb 2024 00:25:31 +0530 [thread overview]
Message-ID: <e1c04f67-5981-4393-8a8e-a28cc53858eb@gmail.com> (raw)
In-Reply-To: <CAP8UFD3F95TzytdpKO=LLf6Y_ejxwh9QtgAxRNKgMXW-72hjgQ@mail.gmail.com>
Hi Patrick, Christian and all,
On 05/02/24 22:13, Christian Couder wrote:
>
> Thanks a lot for these ideas! I have applied your patch and pushed it.
>
Yeah. Thanks for sharing these great ideas! I've submitted the
application using the new ideas page now as mentioned in the parent thread.
>> +### Convert reftable unit tests to use the unit testing framework
>> +
>> +The "reftable" unit tests in "t0032-reftable-unittest.sh"
>> +predate the unit testing framework that was recently
>> +introduced into Git. These tests should be converted to use
>> +the new framework.
>> +
>> +See:
>> +
>> + - this discussion <https://lore.kernel.org/git/cover.1692297001.git.steadmon@google.com/>
>> +
>> +Expected Project Size: 175 hours or 350 hours
>> +
>> +Difficulty: Low
>
> "Difficulty: Low" might not be very accurate from the point of view of
> contributors. I think it's always quite difficult to contribute
> something significant to Git, and sometimes more than we expected.
>
Makes sense. Also, I'm kind of cat-one-the-wall about whether it makes
sense to have two projects about the unit test migration effort itself.
If we're clear that both of them would not overlap, it should be fine.
Otherwise, it would be better to merge them as Patrick suggests.
That said, how helpful would it be to link the following doc in the unit
testing related ideas?
https://github.com/git/git/blob/master/Documentation/technical/unit-tests.txt
>> +### Implement consistency checks for refs
>> +
>>
>> [ ... snip ... ]
>>
>> +
>> + - https://lore.kernel.org/git/6cfee0e4-3285-4f18-91ff-d097da9de737@rd10.de/
>> + - https://lore.kernel.org/git/cover.1706601199.git.ps@pks.im/
>> +
>> [ .... snip ... ]
>> +
>> +### Implement support for reftables in "dumb" HTTP transport
Would it worth linking the reftable technical doc for the above ideas?
https://git-scm.com/docs/reftable
I could see it goes into a lot of detail. I'm just wondering if link to
it would help someone who's looking to learn about reftable.
--
Sivaraam
next prev parent reply other threads:[~2024-02-05 18:55 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 [this message]
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
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=e1c04f67-5981-4393-8a8e-a28cc53858eb@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).