One great thing to include in the log would be the gerrit link that would have the commits in the relevant range. This way developers/QA/users (maybe) could just click the link and quickly be on gerrit and dig through the 30ish commits to try to identify the culprit of the regression.
The bibisect scripts are at: https://gerrit.libreoffice.org/gitweb?p=dev-tools.git;a=tree;f=bibisect;h=39b1fc0779acf014008c64fe8d849d6c4532db94;hb=95e494703c62c7e5dd29a8c36b2ef7f25fa2b88b
migrated from: https://redmine.documentfoundation.org/issues/645
Why am I assigned to this?
(In reply to Joel Madero from comment #1)
> Why am I assigned to this?
Because you were in RedMine and I copied it over ...
Migrating Whiteboard tags to Keywords: (easyHack, topicQA)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
Not my scope
This bibisect builder script isn't used anymore afaik, the current bibisect builds are max repos, where each bibisect commit corresponds to a single source commit (with rare exceptions where consecutive commits failed to build). Closing as WONTFIX.