It's not common practice to use --depth, though, and it'd be nice if there was some kind of upstream based auto-depth system that could say to the cloner "hey, don't bother with changesets older than, oh, two years ago". Or better yet offer some kind of cold storage that an upstream repo could point to for archived changesets, and the ability to dispose of any changesets that have been archived.
It's certainly not as big an issue as binaries, though; have a bunch of textures and even a couple changes each could cause bloat in the tens to hundreds of MB, if not more.
2
u/[deleted] Feb 06 '15
The
--depthargument ofgit cloneis great for dealing with repos that have lots of commits.