Added separate checkout and config file generation to bisect script

build/util/run-bisect-perf-regression.cfg

Index: build/util/run-bisect-perf-regression.cfg
diff --git a/build/util/run-bisect-perf-regression.cfg b/build/util/run-bisect-perf-regression.cfg
new file mode 100644
index 0000000000000000000000000000000000000000..a887a36ea1d647b5b02099c1b5b01b4a677bea10
--- /dev/null
+++ b/build/util/run-bisect-perf-regression.cfg
@@ -0,0 +1,40 @@
+# Copyright (c) 2013 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+"""Config file for Run Performance Test Bisect Tool
+
+This script is intended for use by anyone that wants to run a remote bisection
+on a range of revisions to look for a performance regression. Modify the config
+below and add the revision range, performance command, and metric. You can then
+run a git try <bot>.
+
+Changes to this file should never be submitted.
+
+Args:
+  'command': This is the full command line to pass to the
+      bisect-perf-regression.py script in order to execute the test.
+  'good_revision': An svn revision where the metric hadn't regressed yet.
+  'bad_revision': An svn revision sometime after the metric had regressed.

[tonyg, 2013/02/14 23:30:06]

Aren't these svn or git?

[shatch, 2013/02/14 23:59:46]

Done.

+  'metric': The name of the metric to parse out from the results of the
+      performance test.
+
+
+Sample config:
+
+config = {
+  'command': './out/Release/performance_ui_tests' +
+      ' --gtest_filter=PageCyclerTest.Intl1File',
+  'good_revision': '179755',
+  'bad_revision': '179782',
+  'metric': 'times/t'
+}
+
+"""
+
+config = {
+  'command': '',
+  'good_revision': '',
+  'bad_revision': '',
+  'metric': '',
+}