Re: [PATCH 5/5] Add gitmodules(5)

From: Johannes Sixt <j.sixt@eudaptics.com>
Date: Jun 12, 2007, 11:03 UTC
Message-ID: <466E7D7E.7BAB2FD@eudaptics.com>
In-Reply-To: <8c5c35580706120352y24e53a10sf339147b22f1286e@mail.gmail.com>

Lars Hjemli wrote:

Show 29 quoted lines

> 
> (readded the gitlist)
> 
> On 6/12/07, Johannes Sixt <J.Sixt@eudaptics.com> wrote:
> > Lars Hjemli wrote:
> > > Multiple checkout paths for a single submodule will bring havoc on
> > > this plan, so I need to ask: what is the use-case for multiple
> > > checkout paths?
> >
> > A use-case is the admin directory in the KDE repository. It has:
> >
> > KDE (superproject)
> >  +- kdelibs (subproject)
> >  |   +- admin (subproject)
> >  |   +- subdir1
> >  |   +- ...
> >  +- kdebase (subproject)
> >  |   +- admin (subproject)
> >  |   +- subdir2
> >  |   +- ...
> >  +- kdenetwork (subproject)
> >  |   +- admin (subproject)
> >  |   +- subdir3
> >  |   +- ...
> >  ...
> 
> But in this case, 'admin' isn't a submodule/subproject contained by
> KDE, right? It's contained in three different submodules/subprojects:
> kdelibs, kdebase and kdenetwork.

Notice how kdelibs, kdebase and kdenetwork are both submodule and supermodule: They host the submodule admin and are hosted by KDE.

(If I missed the point, then it's because I didn't follow the discussion; I jumped in because I noticed the symlink proposal by chance.)

-- Hannes