On Thu, 12 Jan 2023 15:41:03 +0100 Diederik de Haas <didi.deb...@cknow.org> wrote: > "Currently, I am using git bisect to narrow down the window of possible > commits, but since the issue appears seemingly random, it will take many > months to identify the offending commit this way." > > Why? It *could* be that the maintainers will wait for the result of the > `git bisect` before responding/acting upon it.
My intention has been to continue with the git bisect. However, I have already encountered two revisions that do not build, so I doubt I can get very far there. I will wait till next week and then report whatever additional information I was able to get through git bisect to the Kernel maintainers. Then I will most likely also tell them that I will not continue with git bisect unless they have a smaller window of revisions for me to try.
