git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: gitster@pobox.com
Cc: chriscool@tuxfamily.org, git@vger.kernel.org, jnareb@gmail.com,
	johannes.schindelin@gmx.de, newren@gmail.com, peff@peff.net,
	Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: Re: Re: RFC][Feature] submodule
Date: Thu, 19 Mar 2020 22:46:26 +0530	[thread overview]
Message-ID: <20200319171626.5723-1-shouryashukla.oo@gmail.com> (raw)
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

  reply	other threads:[~2020-03-19 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 16:32 RFC][Feature] submodule: teach subcommand 'summary' to give summary for nested submodules Shourya Shukla
2020-03-18 19:48 ` [RFC][Feature] " Junio C Hamano
2020-03-19 17:16   ` Shourya Shukla [this message]
2020-03-19 21:33     ` RFC][Feature] submodule Junio C Hamano
2020-03-20 16:08       ` Re: [RFC][Feature] Shourya Shukla
2020-03-24  7:29         ` Christian Couder
  -- strict thread matches above, loose matches on Subject: below --
2020-03-19 17:33 [GSoC][PATCH 2/2] t4131: use helper function to replace test -f <path> Kaartic Sivaraam
2020-03-20 15:39 ` Re: RFC][Feature] submodule Shourya Shukla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200319171626.5723-1-shouryashukla.oo@gmail.com \
    --to=shouryashukla.oo@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).