On Thu, Oct 13, 2016 at 1:15 PM Tong Sun <suntong...@gmail.com> wrote:

> The problem occurs between two consequent 'go get' that may have a long
time span. If
>
> git checkout master
>
> is suppose to fix the problem, then 'go get' should at least try to do
that, I suppose.

It fixes the problem provided no changes were made to the tree. But even if
there are no changes made to the tree in the detached head state, or it
being on a different branch than master, it would be strange if go get just
silently changed the current head state/current branch of a repository
someone intentionally put in such state. It's reasonable to suppose that
someone needs/wants to be on that branch/in that detached head state so
human intervention/supervision is justified, IMO.

-- 

-j

-- 
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.

Reply via email to