On Friday, July 4, 2014 7:23:26 AM UTC+2, Nathan Youngman wrote:
Hi Chris,
That misses my point. I'm using gopkg.in to have multiple major versions
like *.v0 and *.v1 that refer to tags in the source repository. As a
project maintainer, I want to make multiple versions available so people
can upgrade at their leisure.
At the same time, it could make sense to use custom import checking to
disallow directly importing master from github.com.
This is a case not covered by the proposal. Should this combination be
possible? Should it not?
Hi Chris,
That misses my point. I'm using gopkg.in to have multiple major versions
like *.v0 and *.v1 that refer to tags in the source repository. As a
project maintainer, I want to make multiple versions available so people
can upgrade at their leisure.
At the same time, it could make sense to use custom import checking to
disallow directly importing master from github.com.
This is a case not covered by the proposal. Should this combination be
possible? Should it not?
a few emails ago for more details.
Regards,
Alberto
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
