• Eric Paris's avatar
    Split hack/{verify,update}-* files so we don't always go build · 3b7c3965
    Eric Paris authored
    Right now some of the hack/* tools use `go run` and build almost every
    time. There are some which expect you to have already run `go install`.
    And in all cases the pre-commit hook, which runs a full build wouldn't
    want to do either, since it just built!
    
    This creates a new hack/after-build/ directory and has the scripts which
    REQUIRE that the binary already be built. It doesn't test and complain.
    It just fails miserably. Users should not be in this directory. Users
    should just use hack/verify-* which will just do the build and then call
    the "after-build" version. The pre-commit hook or anything which KNOWS
    the binaries have been built can use the fast version.
    3b7c3965
Name
Last commit
Last update
Godeps Loading commit data...
api/swagger-spec Loading commit data...
build Loading commit data...
cluster Loading commit data...
cmd Loading commit data...
contrib Loading commit data...
docs Loading commit data...
examples Loading commit data...
hack Loading commit data...
hooks Loading commit data...
pkg Loading commit data...
plugin Loading commit data...
test Loading commit data...
third_party Loading commit data...
www Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
CHANGELOG.md Loading commit data...
CONTRIB.md Loading commit data...
CONTRIBUTING.md Loading commit data...
DESIGN.md Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
Vagrantfile Loading commit data...
logo.pdf Loading commit data...
logo.png Loading commit data...
logo.svg Loading commit data...
logo_usage_guidelines.md Loading commit data...
shippable.yml Loading commit data...
tmp-valid-pod.json Loading commit data...