[英]"git bisect" tries to test an unexpectedly large number of revisions
When I run:当我跑步时:
git bisect start <bad_commit> <good_commit>
I get:我得到:
Bisecting: 9727 revisions left to test after this (roughly 13 steps)
But the bad_commit and good_commit I specified are clearly only around 50 commits back in history.但是我指定的 bad_commit 和 good_commit 在历史上显然只有大约 50 次提交。 I did a "git log" and saw both of the commits there.
我做了一个“git log”并在那里看到了两个提交。 I also verified the bad commit is more recent than the good commit.
我还验证了错误的提交比良好的提交更新。
What's going on here?这里发生了什么?
If you merged in a long-lived branch bisect by default will hunt through the whole branch.如果你合并到一个长期存在的分支中,默认情况下平分将遍历整个分支。 Easy way to wall off the side histories is to add
--first-parent
, that'll tell you the merge that brought the bug.屏蔽次要历史的简单方法是添加
--first-parent
,它会告诉您带来错误的合并。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.