From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
git@vger.kernel.org, avarab@gmail.com, jrnieder@gmail.com,
albertcui@google.com, matheus.bernardino@usp.br
Subject: Re: RFC/Discussion - Submodule UX Improvements
Date: Tue, 20 Apr 2021 16:30:50 -0700 [thread overview]
Message-ID: <xmqq1rb4355h.fsf@gitster.g> (raw)
In-Reply-To: <YH9drebF84mx2t5r@google.com> (Emily Shaffer's message of "Tue, 20 Apr 2021 16:03:09 -0700")
Emily Shaffer <emilyshaffer@google.com> writes:
> This is actually a point we discussed internally and I cut out of the
> doc before sharing, because it is very far down our roadmap (not
> expecting to address until probably the second half of the year). As I
> understand it, this can also be achieved today by setting
> 'submodule.path/to/module.active = false' in the superproject's
> .git/config.
Yeah, I think we also added support to choose which submodules can
be "active" based on the attributes system.
Three are many ways to apply band-aid to a tree that should have
been a monolithic single repository but has been split into many
submodules only because we historically did not scale well. As you
meantioned, sparse-checkout and lazy/partial cloning may change the
picture drastically, not just "sparse" may allow such an "a set of
artificially split out submodules" to be selectively populated, but
more directly clone and work with only the parts you are interested
in a monolithic repository.
next prev parent reply other threads:[~2021-04-20 23:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 23:36 RFC/Discussion - Submodule UX Improvements Emily Shaffer
2021-04-18 5:22 ` Christian Couder
2021-04-20 23:10 ` Emily Shaffer
2021-04-19 3:20 ` Philippe Blain
2021-04-20 23:03 ` Emily Shaffer
2021-04-20 23:30 ` Junio C Hamano [this message]
2021-04-21 2:27 ` Philippe Blain
2021-04-19 12:56 ` Randall S. Becker
2021-04-19 12:56 ` Aaron Schrab
2021-04-20 18:49 ` Emily Shaffer
2021-04-20 19:29 ` Randall S. Becker
2021-04-19 19:14 ` Jacob Keller
2021-04-19 19:28 ` Randall S. Becker
2021-04-20 16:18 ` Jacob Keller
2021-04-20 18:47 ` Emily Shaffer
2021-04-20 19:38 ` Randall S. Becker
2021-04-21 6:57 ` Jacob Keller
2021-04-22 15:32 ` Jacob Keller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1rb4355h.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=albertcui@google.com \
--cc=avarab@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=levraiphilippeblain@gmail.com \
--cc=matheus.bernardino@usp.br \
/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.
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 NNTP newsgroup(s).