[PATCH 5/5] Add gitmodules(5)
- From
- Lars Hjemli <hjemli@gmail.com>
- Date
- Jun 12, 2007, 10:54 UTC
- Message-ID
- <8c5c35580706120354w69bddb7o8edce484be714087@mail.gmail.com>
- In-Reply-To
- <8c5c35580706120352y24e53a10sf339147b22f1286e@mail.gmail.com>
(readded the gitlist)
On 6/12/07, Johannes Sixt <J.Sixt@eudaptics.com> wrote:
Show 21 quoted lines
> 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.
-- larsh