Documentation: git submodule init --update

[mkoistinen]

Greetings, my first github issue post, please be gentle.

From the documentation in README.md:

git submodule init --update

So I, being the diligent documentation reader types:

$ git submodule init --update
Usage: git submodule [--quiet] add [-b branch] [-f|--force] [--reference <repository>] [--] <repository> [<path>]
   or: git submodule [--quiet] status [--cached] [--recursive] [--] [<path>...]
   or: git submodule [--quiet] init [--] [<path>...]
   or: git submodule [--quiet] update [--init] [-N|--no-fetch] [--rebase] [--reference <repository>] [--merge] [--recursive] [--] [<path>...]
   or: git submodule [--quiet] summary [--cached|--files] [--summary-limit <n>] [commit] [--] [<path>...]
   or: git submodule [--quiet] foreach [--recursive] <command>
   or: git submodule [--quiet] sync [--] [<path>...]
$ git --version
git version 1.7.3.1

Hmmm, perhaps it was meant to be git submodule update --init?

$ git submodule update --init
Cloning into node_modules/semver...
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Clone of 'git@github.com:isaacs/node-semver.git' into submodule path 'node_modules/semver' failed

Nope. Hmmm, how do Install this?

[isaacs]

Duplicate of #578. Closed by d58cefa

[isaacs]

Greetings, my first github issue post, please be gentle.

Also, welcome and thanks! Please post more issues as you encounter them :)

[mkoistinen]

I agree that the first part of this issue is a duplicate (I should've read the latest issues first). But what about the 2nd part? With the requirement of using a private key to get the subs?

[isaacs]

Grrr... submodules.

[isaacs]

Closed by 27d2e35. Grr, submodules.