west init should recursively handle submodules for the manifest repo

To make the workflow west init ... west update fully working for manifest repositories with submodules, west init command should recursively get git submodules.

[mbolivar-nordic]

My point is that I don’t like the name --git-opt because it is ambiguous. In the west init case, --clone-opt is very specific. I would say we could add --diff-opt to west diff and --status-opt to west status for similar reasons. These are not likely to be difficult to remember even though they are different, because the name of the option is right there in the command name.

For west update, a --git-opt is “just wrong” in my opinion. The west update command in particular runs git a lot of times for different purposes and a generic --git-opt option there is particularly confusing.

[marc-hb]

That west init checks out the manifest repo at all made me have different expectations then what it is designed for I think.

That’s a very fair point and in fact in 4th comment above I wrote:

So it would affect west init only when used without -l, correct? Seems fine as long as it’s possible and easy to manually git clone the manifest repo non-recursively and take it from there.

However this all has to be balanced against implementation complexity, other preferences and priorities, “future-proofness” and last but not least limited manpower to deal with it all. For now it seems the person writing 98% of the west code makes the technical decisions (after attentive consultation) and for the coherence and success of the project I hope it stays that way 😃