https://bugs.documentfoundation.org/show_bug.cgi?id=146917
--- Comment #2 from Miklos Vajna <vmik...@collabora.com> --- I think that's not a correct conclusion. Here is what I tried: 1) Clone the linux-64-7.2 bibisect repo. 2) Check out bd4b5b0faf3850b5f5e2e7713504a9cb640941a1 to include the above core.git 76ae0359f35baeb4f8adf1d121c0f974c9024997 commit. 3) Observe the output from the above bugdoc. 4) git checkout HEAD^ to exclude the above core.git commit. 5) Observe that the output for the above bugdoc is unchanged. Which is not too surprising, the above core.git commit is a mechanical refactor, unlikely to result in anything that is possible to observe by a user. Any reason you don't bisect to an exact commit using the linux-64-7.2 bibisect repo, rather just to a range and then guess? -- You are receiving this mail because: You are the assignee for the bug.
