Yes, it's a debatable subject within the Go community. See this blog for example:
https://medium.com/@c9s/golang-the-annoying-remote-import-path-c6c7e76517e5 There are some tricks you can do using a different git remote, `git remote add myfork github.com/yourfork/project` Then when you push, you call `git push myfork master` I am not too keen of using this trick. It's kind of like banging your computer case to fix it. Go paths and dependency management has been broken if you use it in the manner not intended by its original design, and they are fixing it right now. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
