So, it's largely doing the same thing as git submodules, but with slightly fewer commands and more understandable naming. (I'm restating it to make sure my understanding is correct)
This makes me want to suggest the following: 1. rename the `clone` command to something else (perhaps `depend` to create a new dependency). 2) make a new `clone` command whose job it is to git-clone a repo and if it has an `atlas.workspace`, then: a) do the git-clone of all of its projects and dependencies AND 2. activate the `rep` command to checkout all dependencies at the desired commit. Side note: `atlas rep` could be considered to mean "atlas reproduce" in the documentation (as in, reproducing a source code configuration).
