The first commit is a monster. But it didn't actually touch file contents -- it just moves stuff around to match the layout of a proper Go repo. It's basically the result of this:
The latter step is because the latest gorepoman, which supports vendor folders, expects the manifest to be in the managed vendor folder.
(In the future, using gorepoman in here will entail invoking it with a -d parameter, so that it manages the dependencies in the correct location: gorepoman -d ./vendor ...)
If you look at the other two commits, you will see the actual (and very minor) changes, since the repo is now go get-able and should use proper import paths instead of relative imports.
The first commit is a monster. But it didn't actually touch file contents -- it just moves stuff around to match the layout of a proper Go repo. It's basically the result of this:
The latter step is because the latest gorepoman, which supports vendor folders, expects the manifest to be in the managed vendor folder.
(In the future, using gorepoman in here will entail invoking it with a
-dparameter, so that it manages the dependencies in the correct location:gorepoman -d ./vendor ...)If you look at the other two commits, you will see the actual (and very minor) changes, since the repo is now
go get-able and should use proper import paths instead of relative imports.