From: "Ping Yin" <pkufranky@gmail.com>
To: "Lars Hjemli" <hjemli@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFC] git-submodule: multiple-level modules definition
Date: Mon, 3 Mar 2008 20:45:08 +0800 [thread overview]
Message-ID: <46dff0320803030445o6f37e102heda4878c2d865347@mail.gmail.com> (raw)
In-Reply-To: <8c5c35580803030351l2e8d7eedq58108b54bf07dc5c@mail.gmail.com>
On Mon, Mar 3, 2008 at 7:51 PM, Lars Hjemli <hjemli@gmail.com> wrote:
> On Mon, Mar 3, 2008 at 12:02 PM, Ping Yin <pkufranky@gmail.com> wrote:
> >
> > On Mon, Mar 3, 2008 at 2:57 PM, Lars Hjemli <hjemli@gmail.com> wrote:
> > > On Mon, Mar 3, 2008 at 2:47 AM, Ping Yin <pkufranky@gmail.com> wrote:
> > > > But why always
> > > > use git init even when we don't have the local configuration
> > > > requirement?
> > >
> > > We need a way to tell git which of those submodules we are interested
> > > in, i.e. which submodules to clone/fetch during 'git submodule
> > > update'.
> > >
> > Now that's easy with the multiple level module definition. We can now
> > group our modules by hierachy and designate modules we are interested
> > by logical names such as crawler or search as my proposal has
> > mentioned.
>
> Sorry, you've lost me here. How is 'git submodule update' going to
> avoid cloning/fetching all submodules with your proposal?
>
> PS: the supposed work-flow is an initial 'git submodule init foo bar
> baz' (i.e. register the submodules you're interested in checking out)
> followed by an occasional 'git submodule update' (i.e. update all the
> submodules you are interested in).
>
See my first email. In following .gitmodules example, we can use "git
submodule update service" to update all sub-submodules of submodule
"service" (util, imsearch, imcrawler). We don't have to do "git init"
first.
Without the multiple level module definition, "git init" is good idea,
since every time we want to 'git update', we needn't give so many
module paths. However, if we introduce multiple level module
definition, we can define the module groups we are interested such as
crawler, search and the toppest group service. So we just need to type
one or few module names which makes "git init" not so useful.
And it's more flexible by using module name: at one time we can update
"cralwer" module group, and at another time we can update "search"
module group.
.gitmodules example
------------------------------------------------------
[submodule "service"]
submodule = crawler
submodule = search
[submodule "crawler"]
submodule = util
submodule = imcrawter
[submodule "search"]
submodule = util
submodule = imsearch
[submodule "util"] (1)
url = git://xyzzy/util.git
[submodule "imsearch"]
path = search/imsearch
url = git://xyzzy/imsearch.git
[submodule "imcrawler"]
path = crawler/imcrawter
url = git://xyzzy/imcrawter.git
------------------------------------------------------
> --
> lh
>
--
Ping Yin
next prev parent reply other threads:[~2008-03-03 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 17:11 [RFC] git-submodule: multiple-level modules definition Ping Yin
2008-03-02 18:18 ` Lars Hjemli
2008-03-03 1:47 ` Ping Yin
2008-03-03 6:57 ` Lars Hjemli
2008-03-03 11:02 ` Ping Yin
2008-03-03 11:51 ` Lars Hjemli
2008-03-03 12:45 ` Ping Yin [this message]
2008-03-04 13:27 ` 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=46dff0320803030445o6f37e102heda4878c2d865347@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjemli@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.
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).