On Wed, Feb 21, 2018, at 13:49, Peter Bourgon wrote: > > If not, do I maintain separate /v2 and /v3 trees in my directory and > > copy/paste changes between them when I want to release security fixes as a > > point release? > > Yes, this is what vgo expects.
This (and the other alternatives) seem like they break most common source control work flows to me. Any time we force users to change their workflow, I suspect we risk having to back track later. Even in cases where it may be better (eg. GOPATH which, like many people, I fought against when I first started using Go, but later came to love) if you force developers to drastically change their work flow, many of them will either push back, or, if it's only convention as this is, simply won't do it. —Sam -- 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.
