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

[GSoC][RFC] proposal: convert git-submodule to builtin script

From
KAKhalid Ali <khalludi123@gmail.com>
Date
Apr 2, 2019, 20:32 UTC
Message-ID
<CAD8q83SifH-7mKOet-Uuf_KHCqvO2mkxiZgEyQhoNRhshFG_Lg@mail.gmail.com>
Hi,

My name is Khalid Ali and I am looking to convert the git-submodule to a builtin C script. The link below contains my first proposal draft [1] and my microproject is at [2]. My main concern is that my second task is not verbose enough. I am not sure if I should add a specific breakdown of large items within the submodule command.

Outside of the draft, I was wondering whether this should be implemented through multiple patches to the master branch or through a separate, long-running feature branch that will be merged at the end of the GSoC timeline?

Feedback is greatly appreciated!

[1] https://docs.google.com/document/d/1olGG8eJxFoMNyGt-4uMiTD3LjRYx15pttg67AJYliu8/edit?usp=sharing [2] https://public-inbox.org/git/20190402014115.22478-1-khalludi123@gmail.com/

Next: Johannes Schindelin
Message 1 of 4 in “[GSoC][RFC] proposal: convert git-submodule to builtin script”
  1. Khalid AliApr 2, 2019
  2. Johannes SchindelinApr 3, 2019
  3. Khalid AliApr 3, 2019
  4. Christian CouderApr 4, 2019

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.