From: Christian Couder <christian.couder@gmail.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>,
git <git@vger.kernel.org>, Jakub Narebski <jnareb@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Elijah Newren <newren@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: Re: [RFC][Feature]
Date: Tue, 24 Mar 2020 08:29:06 +0100 [thread overview]
Message-ID: <CAP8UFD2nfqRX6+xjRk=F1g+t9T=FgxQVsaNt+b+jW8XoYzuTDQ@mail.gmail.com> (raw)
In-Reply-To: <20200320160813.9242-1-shouryashukla.oo@gmail.com>
On Fri, Mar 20, 2020 at 5:08 PM Shourya Shukla
<shouryashukla.oo@gmail.com> wrote:
>
> > "We want submodule A and B's sub(sub)*modules all the way down
> > to the leaf submodule, but directory C houses many submodules,
> > among which only one can be active, and we want C/X and its
> > sub(sub)*modules all the way down to the leaf but not C/Y nor
> > C/Z or any other C/<anything>."
>
> That's a tough one. Would you advise developing the feature which may
> work atleast for the "normal" cases? In case it does not work for the
> aforementioned case and the like, we classify it as a BUG for further
> correction?
How are the other git-submodule sub-commands working with --recursive?
Shouldn't --recursive work in the same way for all the sub-commands?
prev parent reply other threads:[~2020-03-24 7:29 UTC|newest]
Thread overview: 6+ 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 ` Re: RFC][Feature] submodule Shourya Shukla
2020-03-19 21:33 ` Junio C Hamano
2020-03-20 16:08 ` Re: [RFC][Feature] Shourya Shukla
2020-03-24 7:29 ` Christian Couder [this message]
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='CAP8UFD2nfqRX6+xjRk=F1g+t9T=FgxQVsaNt+b+jW8XoYzuTDQ@mail.gmail.com' \
--to=christian.couder@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 \
--cc=shouryashukla.oo@gmail.com \
/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).