aboutsummaryrefslogtreecommitdiffstats
path: root/compat/regex/regexec.c
diff options
context:
space:
mode:
authorMihail Atanassov <m.atanassov92@gmail.com>2019-10-28 22:01:22 +0000
committerJunio C Hamano <gitster@pobox.com>2019-10-29 11:53:56 +0900
commit8dd327b2465c5d2af62b85cb7974ceec41ab25f2 (patch)
tree08b84613f6d635c1c3f4822c878f96e1f3b4c5c7 /compat/regex/regexec.c
parentGit 2.23 (diff)
downloadgit-8dd327b2465c5d2af62b85cb7974ceec41ab25f2.tar.gz
git-8dd327b2465c5d2af62b85cb7974ceec41ab25f2.zip
Documentation/git-bisect.txt: add --no-ff to merge command
The hotfix application example uses `git merge --no-commit` to apply temporary changes to the working tree during a bisect operation. In some situations this can be a fast-forward and `merge` will apply the hotfix branch's commits regardless of `--no-commit` (as documented in the `git merge` manual). In the pathological case this will make a `git bisect run` invocation loop indefinitely between the first bisect step and the fast-forwarded post-merge HEAD. Add `--no-ff` to the merge command to avoid this issue. Signed-off-by: Mihail Atanassov <m.atanassov92@gmail.com> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'compat/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions