Replacing the forest extension with core functionality
Adrian Buehlmann
adrian at cadifra.com
Wed Apr 9 18:22:58 UTC 2008
On 08.04.2008 20:57, Adrian Buehlmann wrote:
> So the checked out tree of a submodule resides inside a subdirectory
> in P/, so if I use some example directory names, the structure is:
>
> somedir/P/:
> .hg/
> .hgmodules
> <working dir content fed by P/.hg>
> submodule1/
> submodule2/
> submodule3/
>
> with .hgmodules containing:
>
> '''
> [submodule1]
> ..
>
> [submodule2]
> ..
>
> [submodule3]
> ..
> '''
Does that mean submodules have a cloned store beneath P like this (?):
somedir/P/:
.hg/
.hgmodules
<working dir content fed by P/.hg>
submodule1/:
.hg/
<working dir of submodule1>
submodule2/:
.hg/
<working dir of submodule2>
submodule3/:
.hg/
<working dir of submodule3>
so the submodules are in fact sub-repositories and P/.hgmodules
contains the recipe how to clone them?
More information about the Mercurial-devel
mailing list