Why use go get to prepare cache.

[rcio]

I use trash to manage vendor packages from a local forked repo, instead of original one on github or golang.org, consider by more faster git clone speed.

But it still do a slow clone when no trash cache at all, so I looked into then source code, found when trash do a "cache perparing", first it use go get -d -f -u command and the original package name(aka the original repo address) to initial a cache dir. Then add 'Repo' config as a remote, use this remote to fetch or update.

So my question is: why use go get? why not just git init and remote add and fetch?

Since I delete the go get code lines, still get a change to check a if current cache dir is already a git repo, if not, a go init will be executed.