From: "Ping Yin" <pkufranky@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: [RFC] Configurable name(s) for .gitmodules
Date: Sat, 8 Dec 2007 00:00:12 +0800 [thread overview]
Message-ID: <46dff0320712070800j6dd83714j265b3f7b291b855c@mail.gmail.com> (raw)
I have a super project with many submodules. Each kind of role may
check out different set of submodules. There are some common modules
which are almost checked out by every role.
Here comes my question: how to implement this elegantly? If all
submodules are put in the same .gitmodules, every role has to in the
command line manually designate all submodules to be checked out.
However, it's hard to remember which submodules is required by which
role, not to mention the so huge .gitmodules. Maybe a script for each
role can help, but it's a little ugly.
If the name for '.gitmodules' is configurable, we can check in
modules.roleA and modules.roleB, etc. Then role A can designate the
corresponding modules.roleA as .gitmodules. Furtherly, if mutiple
names are allowed, for common modules, we can have modules.common and
then submodule.defaultnames="modules.common, modules.roleA" to avoid
duplicated module name entires in both modules.roleA and
modules.roleB.
I have gone deeply into git-submodule.sh and see
"GIT_CONFIG=.gitmodules" is used. However, configuable multiple names
can't be implemented in this way.
Recap:
1. configurable name for '.gitmodules'
2. better to allow mutiple names
3. the implementation issue for mutiple names
--
Ping Yin
next reply other threads:[~2007-12-07 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 16:00 Ping Yin [this message]
2007-12-10 16:20 ` [RFC] Configurable name(s) for .gitmodules Ping Yin
2007-12-10 16:54 ` Sven Verdoolaege
[not found] ` <20071210165200.GF3490MdfPADPa@greensroom.kotnet.org>
2007-12-10 17:34 ` Ping Yin
2007-12-10 17:35 ` Ping Yin
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=46dff0320712070800j6dd83714j265b3f7b291b855c@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
/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).