Re: [PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size
- From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
- Date
- Jan 9, 2018, 16:01 UTC
- Message-ID
- <3d85256e-4f19-b9d6-323a-d683dbfd8cf7@gmail.com>
- In-Reply-To
- <CAGZ79kYrp_DAaiDzpiWbTSvsfud=JHSO+NX3UaC4osAE3dYmmQ@mail.gmail.com>
On Tuesday 09 January 2018 12:08 AM, Stefan Beller wrote:
Show 14 quoted lines
>> 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? >
Maybe I misunderstood submodules when I wrote that example. Could you help out with a better and precise replacement?
Just putting in some context as to why I did this change, I thought this was the only thing that lacked an example and wanted to make it consistent.
-- Kaartic