| commit | 6e3d45742db9d47fb9ab3b5f61f4dd6c0f532a1d | [log] [tgz] |
|---|---|---|
| author | dnj <dnj@chromium.org> | Fri May 26 20:05:11 2017 |
| committer | Commit bot <commit-bot@chromium.org> | Fri May 26 20:05:11 2017 |
| tree | abc6436734095ba69d97accfe1c17dd3f6126807 | |
| parent | d06ec5035c609eb030e20b470ce6ceeb0d7f428c [diff] |
[vpython] Incorporate interpreter path/hash. VirtualEnv bakes the host Python interpreter's path into its configuration. This means that if the underlying interpreter changes or is replaced, "vpython" will continue using the old specification unquestioningly, potentially leading to some inconsistencies. This approach creates a new message, "Runtime", which represents the Python runtime configuration, including its interpreter hash. Runtime is folded into "vpython"'s environment hash, meaning that if the interpreter changes, "vpython" will assign the new interpreter to a different environment. BUG=None TEST=local Review-Url: https://codereview.chromium.org/2905943002
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.