Small improvements to push-to-trunk.sh and merge-to-branch.sh.
authorjkummerow@chromium.org <jkummerow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 13 Apr 2012 16:00:31 +0000 (16:00 +0000)
committerjkummerow@chromium.org <jkummerow@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 13 Apr 2012 16:00:31 +0000 (16:00 +0000)
commit0e80df8fa8e480944c7835f1fbd7d0848e45404b
tree48dd7a5565872b663f97b7b243c656af2d953d47
parentb1e95913a01bfd825786d4f3939295c99f0d9c6b
Small improvements to push-to-trunk.sh and merge-to-branch.sh.

1.) When a back-merged patch applied at an offset, ignore the "Hunk #1 succeeded at ..." lines instead of printing a scary warning.
2.) When push-to-trunk was not called with "-c /path/to/chrome/src", explicitly ask for the path to help discoverability of the feature.
3.) Correctly convert "BUG=chromium:123" to "(Chromium issue 123)" in the pre-made ChangeLog entry.

Review URL: https://chromiumcodereview.appspot.com/10073010

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11321 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
tools/common-includes.sh
tools/push-to-trunk.sh