From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Tue, 04 Mar 2008 16:12:22 GMT
Subject: Re: [PATCH/RFC v2] git-submodule: multi-level module definition
Message-ID: <alpine.LSU.1.00.0803041608420.22527@racer.site>
In-Reply-To: <1204646661-7776-1-git-send-email-pkufranky@gmail.com>

Hi,

On Wed, 5 Mar 2008, Ping Yin wrote:

> [submodule "service"]
>    submodule = crawler
>    submodule = search
> [submodule "crawler"]
>    submodule = util
>    submodule = imcrawter
> [submodule "search"]
>    submodule = util
>    submodule = imsearch
> [submodule "util"]
>    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

In "git remote", we also have a notion of groups.  It looks much nicer, 
IMO.  So why not do this?

[submodules]
	service = crawler search
	crawler = util imcrawler
	search = util imsearch
[submodule "util"]
    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

However, I think that being able to specify submodule groups recursively 
is only adding to confusion, so I would even prefer this:

[submodules]
	service = util imcrawler imsearch
	crawler = util imcrawler
	search = util imsearch
[...]

Ciao,
Dscho