> So if you're sharing a package with dependencies, you'd have to first check in your dependencies and not rely on go get to manage them. That's what I was des

> So if you're sharing a package with dependencies, you'd have to first check in your dependencies and not rely on go get to manage them. That's what I was describing. The developer of the dependent code pulls in the dependency with go get, and then other developers see both his dependent code and the dependency he was using.