<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILESAVE: DOC/DOCX - Track change of fields not saved correctly" href="https://bugs.documentfoundation.org/show_bug.cgi?id=70234#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILESAVE: DOC/DOCX - Track change of fields not saved correctly" href="https://bugs.documentfoundation.org/show_bug.cgi?id=70234">bug 70234</a> from <a class="email" href="mailto:lo_bugs@iseries-guru.com" title="Terrence Enger <lo_bugs@iseries-guru.com>"> Terrence Enger</a> <pre>Created <a href="http://bugs.documentfoundation.org/attachment.cgi?id=133218" name="attach_133218" title="bibisect results for 4.1 regression">attachment 133218</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=133218&action=edit" title="bibisect results for 4.1 regression">[details]</a> bibisect results for 4.1 regression Thank you, Yosuf, for those STR. A result that can be checked without user interaction works wonderfully with `git bisect run`. Working in the bibisect-42max repository on debian-stretch, I see that the 4.1 regression happened somewhere in the 33 source hashes ... commit s-h date -------- -------- ---------- good 940934b5 db1118a6 2013-11-06 bad d8ba9023 a09f7fdd 2013-11-07 (I expect to be able return to bibisecting in about five hours, unless somebody else gets here first.) Terry.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>