From: Ping Yin Date: Mon, 03 Mar 2008 11:02:26 GMT Subject: Re: [RFC] git-submodule: multiple-level modules definition Message-ID: <46dff0320803030302t286c33a5h3555200c9e8840e3@mail.gmail.com> In-Reply-To: <8c5c35580803022257n7ff0cdc3i1e72a0034d254aa4@mail.gmail.com> On Mon, Mar 3, 2008 at 2:57 PM, Lars Hjemli wrote: > On Mon, Mar 3, 2008 at 2:47 AM, Ping Yin 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. And if there are not a logical module name satisfying our requirement, we can define one by ourself in .git/config (if it's a special or temporary requirement) or in .gitmodules (if it's a common requirement). Now .git/config and .gitmodules will play the same as .git/info/exclude and .gitignore. > -- > larsh > -- Ping Yin