3 ms·

my point was, that if you use git-subrepo instead, then you get exactly that.

• newnewpdro 8y ago
  git already supports `git clone --recursive[-submodules] URL`, there's no need to use git-subrepo to achieve the recursive clone. The problem is the requirement of prior knowledge about the repository's use of submodules. The plain clone won't even report any sort of feedback about the submodules being present and skipped, nor any hint as to how to retrieve them: `git submodule update --init --recursive`. The presence of git-subrepo and `git clone --recursive` is of little consequence from the perspective of the many users who are now familiar with the ubiquitous `git clone URL`. Does github tell people to use git-subrepo to clone a given repository? Hell, does github even tell people to add `--recursive` when a repository uses submodules? I haven't checked, but don't recall ever seeing it do so in the past. These are not difficult technical issues, it's just the sad state of the submodules UX in git. I presume it will improve eventually.
  • keithnz 8y ago
    with git-subrepo, you just clone as normal, you don't even need git-subrepo installed. It just looks like a normal repo. You require 0 prior knowledge. You can update all the code in all the subrepos as a normal repo. Never ever knowing it has subrepos. The only people who need to know and have git-subrepo installed are those that need to sync the subrepos.
    • newnewpdro 8y ago
      Thank you for the clarification, sounds like it's worth taking a closer look.