summaryrefslogtreecommitdiffstats
path: root/android_webview
diff options
context:
space:
mode:
authorsimonhatch@chromium.org <simonhatch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-08-28 18:20:22 +0000
committersimonhatch@chromium.org <simonhatch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-08-28 18:20:22 +0000
commit7154ae4fd9968940ef1e67d5925dbff3575ae8c3 (patch)
tree487d5a4f1d8882b9f8c974b9f2696f03d963c248 /android_webview
parent18516cf967b0fe2c50c1f51a882a3343289e8d63 (diff)
downloadchromium_src-7154ae4fd9968940ef1e67d5925dbff3575ae8c3.zip
chromium_src-7154ae4fd9968940ef1e67d5925dbff3575ae8c3.tar.gz
chromium_src-7154ae4fd9968940ef1e67d5925dbff3575ae8c3.tar.bz2
Try to detect situations where the bisect script can still dive in to V8's "bleeding edge" repository and get back a meaningful result.
At the moment, it tries to detect when both the current revision and previous revisions on trunk are just normal pushes from bleeding edge, and not individual merges. It checks that the description is "Version X.Y.Z" for svn revision N, and then checks that there's a CL in bleeding edge with a description "Prepare to push to trunk. now working on X.Y.(Z+1)". In any other case, the script won't try to dive in any further and just report the version on trunk that it narrowed down to. BUG=279493 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/23620005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220060 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'android_webview')
0 files changed, 0 insertions, 0 deletions