`npm version` should work in a git directory w/o git

If a package seemed to be located in a git directory (for example, if it
was alongside a ".git" directory), but the user did not have git on
their path, npm would throw a cryptic error about calling trim on
undefined.

With this patch, npm will log that git was not found, and that tagging
the version was skipped, but otherwise go on to updating the
package.json file.

This was probably primarily felt by Windows users, where git might be
located within a GUI client, but would be using npm from the command
prompt.
Fix default `loglevel` doc

Default is `"warn"` now.
init-package-json@1.1.1

Properly pick up default values from environment variables.
reconcile init-* config with init-package-json
perl 5.18.x doesn't like -pi without filenames
fstream-npm@1.0.1

Always include LICENSE[.*], LICENCE[.*], CHANGES[.*], CHANGELOG[.*], and
HISTORY[.*].
request@2.46.0

Tests and cleanup.
update changelog for npm@2.1.6
2.1.6
npm-registry-client@4.0.0

* Explicitly pass auth into all calls.
* Reworked the npm-registry-client API for consistency.
* Break registry client dependency on npm's cache.
* Remove getAll logic (moved to lib/cache/update-index.js).
* Decouple config from npm / npmconf.
* Remove bugs and upload because they're unused.
nerf better

Fixes npm/npm-registry-client#77, partially addresses
npm/npm-registry-client#70.
use new npm-registry-client API

Makes a *lot* clearer when the CLI is doing something with auth
implications, by explicitly pass auth to registry client.  Moves lookup
of credentials into mapRegistryToURI, which makes the code more
consistent.
style tweaks
directly cache search metadata
handle caching of metadata in npm itself
add npmconf → registry client config adapter
npm-registry-client@4.0.1

Allow users to publish modules with the same name as built-in modules.
tar@1.0.2

Cleaner error handling.
request@2.47.0
update changelog for npm@2.1.7