| commit | 6553a52aeef59501c0b106ff07113b83ad6d179a | [log] [tgz] |
|---|---|---|
| author | charliea <charliea@chromium.org> | Wed Jul 12 13:59:13 2017 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Jul 12 13:59:13 2017 |
| tree | 8f7478e833d61541b0c928b28bfab71f38a880be | |
| parent | 3f5ae6c4a1c17663c8113708a912fea6d8b98781 [diff] |
Flesh out the mmutex binary wrapper and test for existence of lockfile The logic in this CL is uninteresting, but I mostly want to make sure that the wrapper, directory structure, and test harness are set up correctly before getting too much further. BUG=416072 Review-Url: https://codereview.chromium.org/2980603003
go get -u github.com/luci/luci-go/client/cmd/... go get -u github.com/luci/luci-go/server/cmd/...
/common/... and /server/..../appengine/..., /client/... and /server/...; for example, the structures used by the server APIs. These are inherently APIs./appengine/....go1 contains the stable code.master constains the latest code.user.email and user.name are configured in git config.go get -u -t github.com/luci/luci-go/client/...go get -u github.com/maruel/pre-commit-go/cmd/... && pcgRun the following to setup the code review tool and create your first review:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" cd $GOROOT/github.com/luci/luci-go git checkout -b work origin/master # hack hack git commit -a -m "This is awesome\nR=joe@example.com" # This will ask for your Google Account credentials. git cl upload -s # Wait for LGTM over email. # Check the commit queue box in codereview website. # Wait for the change to be tested and landed automatically.
Use git cl help and git cl help <cmd> for more details.