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

Re: Re: RFC][Feature] submodule

From
Shourya Shukla <shouryashukla.oo@gmail.com>
Date
Mar 19, 2020, 17:16 UTC
Message-ID
<20200319171626.5723-1-shouryashukla.oo@gmail.com>
In-Reply-To
<xmqqh7ylfnqi.fsf@gitster.c.googlers.com>
Hello Junio,
> If "git submodule summary --recursive" errors out with today's code,
> no sane user would be using it for any useful purpose, so I would
> think it is OK to add such a feature.
Sure thing! I will try to plan some makeshift implementation.
> If it makes a usable UI for large projects that you can only choose
> between "include no subsubmodules" (i.e. with --no-recursive) or
> "include all sub(sub)*modules" (i.e. with --recursive) is another
> matter, though.

I think discussing this idea may be a good approach right now? What you are saying for large projects does provoke thought though.. Also, what do you think may become a problem for large projects in here?

Thank you so much for the feedback BTW :)

Regards, Shourya Shukla

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “RFC][Feature] submodule: teach subcommand 'summary' to give summary for nested submodules”
  1. Shourya ShuklaMar 18, 2020
  2. Junio C HamanoMar 18, 2020
  3. Shourya ShuklaMar 19, 2020
  4. Junio C HamanoMar 19, 2020
  5. Shourya ShuklaMar 20, 2020
  6. Christian CouderMar 24, 2020

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.