gclient: diff against hash in DEPS
When someone runs "gclient diff", they expect to be diffing their local state against the state of a clean gclient checkout. Up until now, "gclient diff" has been doing... not that. It's been assuming that the sha1 in DEPS is approximately the head of the remote's master branch, finding the merge-base between the local content and that remote master, and diffing against that merge-base. This makes basically no sense in the context of gclient. With gclient, we already know exactly what should be checked out: it's whatever is in DEPS. This CL updates the behavior of "gclient diff" to do the right thing. Bug: 731701 Change-Id: I23a43cbc0d6bc7772495097ff615d4d070f5ad19 Reviewed-on: https://chromium-review.googlesource.com/914717Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Aaron Gable <agable@chromium.org>
Showing
Please
register
or
sign in
to comment