https://bugs.documentfoundation.org/show_bug.cgi?id=170205
--- Comment #12 from Buovjaga <[email protected]> --- (In reply to bugzilla2 from comment #10) > As far as I understood, bibisecting means I have to find out not only the > first build that has the issue, but the exact commit that caused the > regression? That for I need a working and a non working build, and I am not > sure if a "working" 26.2 build exists ... You first check with `git checkout oldest` that the issue is not seen and then with `git checkout master` that it is seen. I'm not sure, if it is still needed, but as the 26.2 repository was recently rebuilt with the new Visual Studio 2022 baseline, I had to manually add the "oldest" tag: git tag oldest cc9574aa24614d168ead5ace2fcc96267347279f We can find out the first commit by saying `git log --reverse` -- You are receiving this mail because: You are the assignee for the bug.
