From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: peff@peff.net, gitster@pobox.com, jrnieder@gmail.com,
johannes.schindelin@gmail.com, Jens.Lehmann@web.de,
ericsunshine@gmail.com, j6t@kdbg.org, hvoigt@hvoigt.net,
Stefan Beller <sbeller@google.com>
Subject: [RFC PATCH 0/5] Submodule Groups
Date: Tue, 24 Nov 2015 17:32:14 -0800 [thread overview]
Message-ID: <1448415139-23675-1-git-send-email-sbeller@google.com> (raw)
This is also available at https://github.com/stefanbeller/git/tree/submodule-groups
It applies on top of the submodule-parallel-patch series I sent a few minutes ago.
Consider having a real large software project in Git with each component
in a submodule (such as an operating system, Android, Debian, Fedora,
no toy OS such as https://github.com/gittup/gittup as that doesn't quite
demonstrate the scale of the problem).
If you have lots of submodules, you probably don't need all of them at once,
but you have functional units. Some submodules are absolutely required,
some are optional and only for very specific purposes.
This patch series adds meaning to a "groups" field in the .gitmodules file.
So you could have a .gitmodules file such as:
[submodule "gcc"]
path = gcc
url = git://...
groups = default,devel
[submodule "linux"]
path = linux
url = git://...
groups = default
[submodule "nethack"]
path = nethack
url = git://...
groups = optional,games
and by this series you can work on an arbitrary subgroup of these submodules such
using these commands:
git clone --group default --group devel git://...
# will clone the superproject and recursively
# checkout any submodule being in at least one of the groups.
git submodule add --group default --group devel git://... ..
# will add a submodule, adding 2 submodule
# groups to its entry in .gitmodule
# as support for clone we want to have:
git config submodule.groups default
git submodule init --groups
# will init all submodules from the default group
# as support for clone we want to have:
git config submodule.groups default
git submodule update --groups
# will update all submodules from the default group
Any feedback welcome, specially on the design level!
(Do we want to have it stored in the .gitmodules file? Do we want to have
the groups configured in .git/config as "submodule.groups", any other way
to make it future proof and extend the groups syntax?)
Thanks,
Stefan
Stefan Beller (5):
submodule-config: keep submodule groups around
git submodule add can add a submodule with groups
git submodule init to pass on groups
submodule--helper: module_list and update-clone have --groups option
builtin/clone: support submodule groups
Documentation/git-clone.txt | 11 ++++
Documentation/git-submodule.txt | 8 ++-
builtin/clone.c | 33 ++++++++++-
builtin/submodule--helper.c | 68 ++++++++++++++++++++++-
git-submodule.sh | 20 ++++++-
submodule-config.c | 14 +++++
submodule-config.h | 2 +
t/t7400-submodule-basic.sh | 118 ++++++++++++++++++++++++++++++++++++++++
t/t7406-submodule-update.sh | 32 +++++++++++
9 files changed, 299 insertions(+), 7 deletions(-)
--
2.6.1.261.g0d9c4c1
next reply other threads:[~2015-11-25 1:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 1:32 Stefan Beller [this message]
2015-11-25 1:32 ` [PATCH 1/5] submodule-config: keep submodule groups around Stefan Beller
2015-11-25 1:32 ` [PATCH 2/5] git submodule add can add a submodule with groups Stefan Beller
2015-11-25 1:32 ` [PATCH 3/5] git submodule init to pass on groups Stefan Beller
2015-11-25 1:32 ` [PATCH 4/5] submodule--helper: module_list and update-clone have --groups option Stefan Beller
2015-11-25 1:32 ` [PATCH 5/5] builtin/clone: support submodule groups Stefan Beller
2015-11-25 17:52 ` Jens Lehmann
2015-11-25 18:08 ` Stefan Beller
2015-11-25 19:50 ` Jens Lehmann
2015-11-25 20:03 ` Stefan Beller
2015-11-25 22:30 ` Jens Lehmann
2015-11-25 22:51 ` Stefan Beller
2015-11-26 0:31 ` [PATCHv2] " Stefan Beller
2015-11-26 0:33 ` Stefan Beller
2015-11-26 5:00 ` Trevor Saunders
2015-11-30 19:31 ` Stefan Beller
2015-12-01 6:53 ` Michael J Gruber
2015-12-01 18:58 ` Stefan Beller
2015-11-25 17:35 ` [RFC PATCH 0/5] Submodule Groups Jens Lehmann
2015-11-25 18:00 ` Stefan Beller
2015-11-25 19:18 ` Jens Lehmann
2015-11-30 23:54 ` Stefan Beller
2015-12-01 22:06 ` Jens Lehmann
2015-11-25 17:50 ` Jens Lehmann
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=1448415139-23675-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=ericsunshine@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=j6t@kdbg.org \
--cc=johannes.schindelin@gmail.com \
--cc=jrnieder@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).