我遇到的问题是两个版本的Linux内核之间的代码更改导致了问题。 在使用git bisect ，我发现由于linux内核中不相关的问题（图形损坏）导致无法追踪原始问题，因此无法缩小原始问题。
使用git bisect ，有两种选择：好的或坏的; 在这种情况下，由于无关的问题，我无法将补丁标记为“好”。
我是否根据git bisect标记该补丁“bad”或者我还做其他事情？
I am having an issue where a code change between two versions of the linux kernel is causing an issue. While using git bisect, I find that I can't narrow down the original problem because of an unrelated problem in the linux kernel (graphics corruption) that makes it impossible to track down the original issue.
With git bisect, there are two choices: good or bad; and in this case I can't mark the patch 'good' because of the unrelated issue.
Do I mark that patch 'bad' according to git bisect or do I do something else?
最满意答案
git不会强迫你使用它给你的提交。 使用git reset --hard othercommit您可以选择另一个提交来测试并继续进行二等分。 使用git bisect skip你可以让git自动选择一个不同的提交（并将有问题的提交标记为已跳过，因此不会再次选择它）。 您还可以标记一系列提交以进行跳过，手册页中包含信息。
当然，如果您碰巧修复了阻止您测试该提交的问题，那么在bisect为您提交提交后，您总是可以应用补丁。
git doesn't force you to use the commit it gives you. With git reset --hard othercommit you can choose another commit to test and continue bisecting from. With git bisect skip you can let git choose a different commit automatically (and mark the problematic commit as skipped so it won't be chosen again). You can also mark a range of commits for skipping, the man page has the information.
Of course you can always apply a patch after bisect gives you a commit if you happen to have a fix for the problem that prevents you from testing that commit.
更多推荐
发布评论