If you happen to have a newer version of some other dependency sitting in your GOPATH, running `godep save` will pick it up as well. To avoid that, you can run:

```
$ godep restore
$ godep save ./...
```

Does that command sequence make sense? Is it intuitive why it works?

And is it inconvenient? I've also contemplated making `save` only add new things and leave existing deps alone (like `go get` default behavior) and having a `save -u` flag or something similar when you do want to update.

I'm very interested in opinions about this.