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

Re: Git in GSoC 2025

From
shejialuo <shejialuo@gmail.com>
Date
Feb 4, 2025, 02:29 UTC
Message-ID
<Z6F7ntBsp1CSflkL@ArchLinux>
In-Reply-To
<cd90cf17-6113-4634-a774-6df707b73e95@gmail.com>
On Sun, Feb 02, 2025 at 05:22:05PM +0530, Kaartic Sivaraam wrote:
Show 20 quoted lines
> Hello Christian, Karthik, Jialuo, Patrick and all,
> 
> On 28/01/25 23:00, Kaartic Sivaraam wrote:
> > 
> > Thank you for suggesting these ideas, Patrick! I've incorporated them
> > into a draft ideas page for now. You can see them here:
> > 
> > https://git.github.io/SoC-2025-Ideas/
> > 
> > Kindly suggest any corrections to the description, project size /
> > difficulty as necessary. I've mentioned potential mentors based on what
> > I'm aware of so far.
> > 
> > Patrick, Christian and Karthik, kindly mention the ideas that you're
> > interested to mentor.
> > 
> 
> Gentle reminder that the ideas list needs completion. Specifically, the
> following ideas only list Patrick as a potential mentor:
> 
Thanks for the reminder.
>   - Refactoring in order to reduce Git’s global state
> 

Although I never code for this, I have reviewed a lot of patches others work on. So, I think I could co-mentor this.

Show 12 quoted lines
>   - Machine-Readable Repository Information Query Tool
> 
> The following idea mentions Karthik and Patrick as potential
> mentors.
> 
>   - Implement support for reftables in “dumb” HTTP transport
> 
> The following idea mentions Jialuo and Patrick as potential
> mentors.
> 
>   - Consolidate ref-related functionality into git-refs
> 
I am OK wth this.
> It would helpful if you all could chime in to let me know if the
> existing allocation is fine and to what other projects you need
> to be mentioned as potential mentors.
> 
In conclusion, I could cover two projects as a co-mentor.

Thanks, Jialuo

> --
> Sivaraam
Previous: Karthik NayakNext: Kaartic Sivaraam
Message 9 of 52 in “Git in GSoC 2025”
  1. Kaartic SivaraamJan 19, 2025
  2. Patrick SteinhardtJan 20, 2025
  3. shejialuoJan 20, 2025
  4. Oswald BuddenhagenJan 21, 2025
  5. Kaartic SivaraamJan 28, 2025
  6. Kaartic SivaraamFeb 2, 2025
  7. Patrick SteinhardtFeb 3, 2025
  8. Karthik NayakFeb 3, 2025
  9. shejialuoFeb 4, 2025
  10. Kaartic SivaraamFeb 4, 2025
  11. Christian CouderFeb 5, 2025
  12. Kaartic SivaraamFeb 7, 2025
  13. Christian CouderFeb 7, 2025
  14. Patrick SteinhardtFeb 7, 2025
  15. Kaartic SivaraamFeb 11, 2025
  16. Ghanshyam ThakkarFeb 16, 2025
  17. Kaartic SivaraamFeb 16, 2025
  18. Junio C HamanoFeb 16, 2025
  19. Ghanshyam ThakkarFeb 17, 2025
  20. Karthik NayakMar 7, 2025
  21. Kaartic SivaraamMar 20, 2025
  22. Karthik NayakMar 21, 2025
  23. shejialuoFeb 8, 2025
  24. Karthik NayakFeb 10, 2025
  25. Christian CouderJan 20, 2025
  26. Patrick SteinhardtJan 20, 2025
  27. Junio C HamanoJan 21, 2025
  28. Kaartic SivaraamJan 30, 2025
  29. Patrick SteinhardtJan 30, 2025
  30. Christian CouderJan 30, 2025
  31. Patrick SteinhardtJan 30, 2025
  32. Junio C HamanoJan 30, 2025
  33. Junio C HamanoJan 30, 2025
  34. Patrick SteinhardtJan 31, 2025
  35. Junio C HamanoJan 31, 2025
  36. Patrick SteinhardtFeb 3, 2025
  37. Patrick SteinhardtJan 31, 2025
  38. Junio C HamanoFeb 3, 2025
  39. Kaartic SivaraamFeb 4, 2025
  40. Kaartic SivaraamJan 30, 2025
  41. Karthik NayakJan 20, 2025
  42. shejialuoJan 20, 2025
  43. Kaartic SivaraamFeb 28, 2025
  44. shejialuoFeb 28, 2025
  45. Patrick SteinhardtFeb 28, 2025
  46. Christian CouderFeb 28, 2025
  47. Ghanshyam ThakkarFeb 28, 2025
  48. Kaartic SivaraamMar 1, 2025
  49. Karthik NayakMar 3, 2025
  50. Patrick SteinhardtJan 27, 2025
  51. shejialuoJan 27, 2025
  52. Kaartic SivaraamJan 28, 2025

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.