git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Add ideas for GSoC 2024

From
Christian Couder <christian.couder@gmail.com>
Date
Feb 6, 2024, 08:13 UTC
Message-ID
<CAP8UFD2yFr1uOjKOnMjznjR6BEzGqq=R7K85z2Jz4i=sG0CLJA@mail.gmail.com>
In-Reply-To
<ZcHIxcrKbgyhdyWn@tanuki>
On Tue, Feb 6, 2024 at 6:51 AM Patrick Steinhardt <ps@pks.im> wrote:
> On Tue, Feb 06, 2024 at 12:25:31AM +0530, Kaartic Sivaraam wrote:
Show 17 quoted lines
> > 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.
>
> I don't quite mind either way. I think overall we have enough tests that
> can be converted even if both projects got picked up separately. And the
> reftable unit tests are a bit more involved than the other tests given
> that their coding style doesn't fit at all into the Git project. So it's
> not like they can just be copied over, they definitely need some special
> care.
>
> Also, the technical complexity of the "reftable" backend is rather high,
> which is another hurdle to take.
>
> Which overall makes me lean more towards keeping this as a separate
> project now that I think about it.

Ok, for me. If we have a contributor working on each of these 2 projects, we just need to be clear that the contributors should not work together on the 2 projects as I think the GSoC forbids that.

Show 6 quoted lines
> > 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
>
> Makes sense to me.
To me too.
Show 8 quoted lines
> > 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.
>
> Definitely doesn't hurt.
I agree.
Thanks!
Previous: Patrick SteinhardtNext: Kaartic Sivaraam
Message 15 of 33 in “Git in GSoC 2024”
  1. Kaartic SivaraamJan 29, 2024
  2. Christian CouderJan 30, 2024
  3. Patrick SteinhardtJan 30, 2024
  4. Patrick SteinhardtJan 31, 2024
  5. Kaartic SivaraamJan 31, 2024
  6. Kaartic SivaraamJan 31, 2024
  7. Karthik NayakFeb 1, 2024
  8. Patrick SteinhardtFeb 1, 2024
  9. Kaartic SivaraamFeb 3, 2024
  10. Kaartic SivaraamFeb 4, 2024
  11. Add ideas for GSoC 2024Patrick Steinhardt, Feb 5, 2024
  12. Christian CouderFeb 5, 2024
  13. Kaartic SivaraamFeb 5, 2024
  14. Patrick SteinhardtFeb 6, 2024
  15. Christian CouderFeb 6, 2024
  16. Kaartic SivaraamFeb 8, 2024
  17. Patrick SteinhardtFeb 9, 2024
  18. Christian CouderFeb 9, 2024
  19. Patrick SteinhardtFeb 6, 2024
  20. Christian CouderFeb 6, 2024
  21. Christian CouderFeb 5, 2024
  22. Kaartic SivaraamFeb 5, 2024
  23. Kaartic SivaraamFeb 21, 2024
  24. Patrick SteinhardtFeb 21, 2024
  25. Christian CouderFeb 21, 2024
  26. Karthik NayakFeb 21, 2024
  27. Kaartic SivaraamFeb 22, 2024
  28. Patrick SteinhardtFeb 22, 2024
  29. Karthik NayakFeb 22, 2024
  30. Christian CouderFeb 22, 2024
  31. Kaartic SivaraamFeb 22, 2024
  32. Patrick SteinhardtFeb 22, 2024
  33. Kaartic SivaraamFeb 24, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.