https://bugs.documentfoundation.org/show_bug.cgi?id=170205
--- Comment #11 from Buovjaga <[email protected]> --- (In reply to bugzilla2 from comment #10) > Can't that be bibisected in the 25.8 branch too? Because in 25.8 I already > know at least the first build that introduced that behavior. In 26.2 I would > have to start from scratch again, as I only know that it does happen in 26.2 > Beta 1 so far. Maybe all 26.2 builds have that bug, can it than be > bibisected at all with that branch? > > 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 ... > > If I totally misunderstood the process of bibisecting please tell me. Never > did that before ... It would still be the same ~13 steps. The benefit is that you immediately get the "mother" commit. -- You are receiving this mail because: You are the assignee for the bug.
