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

Re: [GSoC] Proposal Discussion: git-refs Project

From
Patrick Steinhardt <ps@pks.im>
Date
Mar 24, 2025, 12:02 UTC
Message-ID
<Z-FJ3EQdFIkQgtkR@pks.im>
In-Reply-To
<CAMvj1+rbYKFNeWEvvN76MTpzfuWc4TN4ViXRE4nTfWy7ZMspWg@mail.gmail.com>
Hi Yuting,
On Sun, Mar 23, 2025 at 09:36:51PM +0800, Yuting Zheng wrote:
Show 22 quoted lines
> Dear Git Community,
> 
> I am very interested in applying for the GSoC 2025 project "Consolidate
> ref-related functionality into git-refs". I have reviewed the relevant
> code, documentation, and mailing lists, and as part of the application
> prerequisites, I have submitted a microproject patch
> (https://lore.kernel.org/git/20250323022111.20226-1-05ZYT30@gmail.com/).
> 
> My current idea is to extend the `git-refs` command—by calling into the
> existing code—to add subcommands. This approach would replace the
> functionalities of the mentioned commands while ensuring that I do not
> modify the code underlying them. This guarantees that the new `git-refs`
> subcommand meets the new requirements without affecting the usage of the
> existing commands.
> 
> However, when searching the mailing lists with keywords
> “nq:consolidate ref” and “s: refs”, I did not find any discussion about
> merging these commands. If anyone has come across any previous discussions
> or could kindly provide additional insights on this matter, I would greatly
> appreciate your help.
> 
> Thank you for your guidance.

I have been chatting with Peff about this topic quite a while ago, but that was mostly an in-person chat that hasn't made it onto the mailing list. I may also have mentioned on the mailing list on several occasions that it would make sense to consolidate, but there wasn't ever a bigger discussion around all of this. There's also [1] as a non-authoritative source for this project that documents my intent to consolidate the commands.

So ultimately there hasn't been a lot of discussion yet around this whole thing. Driving consensus and designing the new interface would thus be one of the biggest challenges in this project from my point of view.

I'm happy to provide more feedback once an initial draft has been created for how the project could look like!

Thanks.
Patrick
[1]: https://gitlab.com/gitlab-org/git/-/issues/330
Previous: Yuting ZhengNext: Yuting Zheng
Message 2 of 17 in “[GSoC] Proposal Discussion: git-refs Project”
  1. Yuting ZhengMar 23, 2025
  2. Patrick SteinhardtMar 24, 2025
  3. Yuting ZhengMar 27, 2025
  4. shejialuoMar 28, 2025
  5. Yuting ZhengMar 29, 2025
  6. [GSoC] git-refs proposal draftZheng Yuting, Mar 29, 2025
  7. Patrick SteinhardtMar 31, 2025
  8. Yuting ZhengApr 1, 2025
  9. Patrick SteinhardtApr 2, 2025
  10. Discussion on git-refs list Implementation and Possible ApproachesZheng Yuting, Apr 3, 2025
  11. Karthik NayakApr 4, 2025
  12. Yuting ZhengApr 4, 2025
  13. Patrick SteinhardtApr 4, 2025
  14. Yuting ZhengApr 4, 2025
  15. Yuting ZhengApr 4, 2025
  16. [GSoC] git-refs proposal v2Yuting Zheng, Apr 6, 2025
  17. Fwd: Discussion on git-refs list Implementation and Possible ApproachesYuting Zheng, Apr 4, 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.