threads / discuss / 32646

git fetch without --recurse-submodules option

Subject: git fetch without --recurse-submodules option

## tl;dr

2 messages between Jan 16, 2013 and Jan 16, 2013.

replies: 1people: 2as markdown or json

乙酸鋰· Jan 16, 2013, 05:45 UTC · lore

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· Jan 16, 2013, 18:24 UTC · re: 乙酸鋰 · lore

Re: git fetch without --recurse-submodules option

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.

Show 5 quoted lines
> 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.

← back to recent threads