f0532662fb
merge_to_branch.py can fail partway through for many reasons (the EDITOR environment variable not being set being one) and on the next run this leads to an error saying: Exception: A merge is already in progress It is not obvious to those doing their first merge how to get past this. Searching the source code leads to the -f option but it should be possible to proceed without searching the source. This change adds "Use -f to continue" to the message. Change-Id: Ic9d8e404e044be3308e5ae3ef3a4430e4aa3ccc2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1837028 Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#64096} |
||
---|---|---|
.. | ||
testdata/v8/third_party/googletest/src/googletest/include/gtest | ||
auto_push.py | ||
auto_roll.py | ||
auto_tag.py | ||
check_clusterfuzz.py | ||
common_includes.py | ||
create_release.py | ||
filter_build_files.py | ||
git_recipes.py | ||
merge_to_branch.py | ||
mergeinfo.py | ||
PRESUBMIT.py | ||
push_to_candidates.py | ||
roll_merge.py | ||
script_test.py | ||
search_related_commits.py | ||
test_mergeinfo.py | ||
test_scripts.py | ||
test_search_related_commits.py |