`glide update` or a install should do the job, yes.
If that does not `mv vendor _vendor && glide install` to figure out if
things works or are stinky.
Do you mean you re in situation where you have one to many repo to update
by doing a fork / PR / merge
to actually make a significant change
Can it work when the forked gh repo contains many packages that sometimes
use each other?
It feels weird to be masking the very repo I cloned to work in...
Now I am using the approach outlined by Francesc Campoy in
http://blog.campoy.cat/2014/03/github-and-go-forking-pull-requests-and.html
Neat
