Use shallow clones for non-development situations

[dabrahams]

When the user is just installing or testing, consider doing a shallow clone. From git-clone's man page:

--depth

Create a shallow clone with a history truncated to the specified number of revisions. A shallow repository has a number of limitations (you cannot clone or fetch from it, nor push from nor into it), but is adequate if you are only interested in the recent history of a large project with a long history, and would want to send in fixes as patches.