On Mon, Mar 3, 2008 at 12:02 PM, Ping Yin <pkufranky@xxxxxxxxx> wrote: > > On Mon, Mar 3, 2008 at 2:57 PM, Lars Hjemli <hjemli@xxxxxxxxx> wrote: > > On Mon, Mar 3, 2008 at 2:47 AM, Ping Yin <pkufranky@xxxxxxxxx> 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). -- lh -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
