# git fetch without --recurse-submodules option 2 messages from 2013-01-16 to 2013-01-16. Participants: 乙酸鋰, Jens Lehmann. Thread: https://gitlist.dev/t/32646 ## 乙酸鋰, 2013-01-16 05:45 Subject: git fetch without --recurse-submodules option Message-ID: URL: https://gitlist.dev/e/CAHtLG6RE-xGYsp-Apcu3hk8OVck%2BHLYZdBtWvcweaBNetwtKNA%40mail.gmail.com ``` Hi, With git pull or git fetch without specifying --recurse-submodules, what is the default action? It seems git fetches submodules wtihout specifying --recurse-submodules. If this is not clear, please update documentation. In git pull document --recurse-submodules option, it tells users to see git-config(1) and gitmodules(5), but does not tell users to refer to git fetch --recurse-submodules for the meaning of the switches. In git fetch document --recurse-submodules option, it does not tell users to see git-config(1) or gitmodules(5). ``` ## Jens Lehmann, 2013-01-16 18:24 Subject: Re: git fetch without --recurse-submodules option Message-ID: <50F6F076.8030305@web.de> URL: https://gitlist.dev/e/50F6F076.8030305%40web.de In-Reply-To: ``` Am 16.01.2013 06:45, schrieb 乙酸鋰: > With git pull or git fetch without specifying --recurse-submodules, > what is the default action? on-demand fetch (unless something else is configured). > It seems git fetches submodules wtihout specifying --recurse-submodules. > If this is not clear, please update documentation. You are right, the documentation for pull and fetch does not state explicitly that "on-demand" is the default here when the option is not used. > In git pull document --recurse-submodules option, it tells users to > see git-config(1) and gitmodules(5), but does not tell users to refer > to git fetch --recurse-submodules for the meaning of the switches. > In git fetch document --recurse-submodules option, it does not tell > users to see git-config(1) or gitmodules(5). Thanks for pointing that out. Unless anyone else wants to improve the documentation I'll look into that in my next git time slot. ```