On Sat, Jan 6, 2018 at 10:46 AM, Kaartic Sivaraam <kaartic.sivar...@gmail.com> wrote: > Signed-off-by: Kaartic Sivaraam <kaartic.sivar...@gmail.com> > --- > Documentation/gitsubmodules.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt > index cb795c6b6..3f73983d5 100644 > --- a/Documentation/gitsubmodules.txt > +++ b/Documentation/gitsubmodules.txt > @@ -63,6 +63,9 @@ Submodules can be used for at least two different use cases: > * Transfer size: > In its current form Git requires the whole working tree present. It > does not allow partial trees to be transferred in fetch or clone. > + If you have your project as multiple repositories tied together as > + submodules in a superproject, you can avoid fetching the working > + trees of the repositories you are not interested in.
You do not fetch a working tree, but a whole repository? > * Access control: > By restricting user access to submodules, this can be used to implement > read/write policies for different users. > -- > 2.16.0.rc0.223.g4a4ac8367 >
