Alexander Morozov

@runcom it works for me with `go version go1.9.2 linux/amd64`. What's your OS and go version?

I am not sure I understand the problem. I thought `vndr ` were supposed to download package to vendor directory, though I might remember wrong. Do you have example repo...

@DmitriyMV is this with `vndr init`? Just `vndr` isn't supposed to download anything, not in `vendor.conf` because otherwise, you could end with some weird `appengine` code.

@DmitriyMV I suppose it might be windows problem :/ It works correctly for me. Can you try again to confirm? Then I'll try to get windows box to test.

@DmitriyMV I don't understand. Did you do `vndr init` to get that `vendor.conf`? There can't be package in `vendor` if it isn't listed in `vendor.conf`.

This happens when package is found in `$GOPATH`. I'll try to fix that this week.

@AkihiroSuda that's a bummer. I wonder if it's easy to detect and produce warnings. Thanks for taking a look.

@resouer I used awk script for that which I lost :( Will appreciate help with that.

We had this idea some day, but problem is that branches can have '@' and many other imaginable symbols in their names. I only see this is as some form...

Omg, sorry, folks - Gmail ate my github label and I missed. Will review today.