Re: [go-nuts] File organization in a github-ed Go project

If someone wanted to fork your library for one of their programs, they could also vendor the package with their changes until it's changed significantly enough that they think it's worth updating to its own namespace (and at that point, it really should be a different import path..) On Mon, Feb 27

[go-nuts] File organization in a github-ed Go project

Hello All, I'm writing my first Go program, it is on GitHub monimelt and I'm specifically talking of the commit 15a7fbc61e141d62655 (master branch). See this questio