<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - clear reproducible error with combination of shared formulas, parallelized computing, autocalc weakness, see comment c#10 | was: Copying by dragging calculates false values (different every time)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124577#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - clear reproducible error with combination of shared formulas, parallelized computing, autocalc weakness, see comment c#10 | was: Copying by dragging calculates false values (different every time)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124577">bug 124577</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to b. from <a href="show_bug.cgi?id=124577#c14">comment #14</a>) > still odd with below ver., > @Telesto: imho those comments are valid and neccessary, and helpful as they > ease the work of the devs by some steps in boiling down which can be done by > 'nopros' like me, Checking if it's a regression and bibisecting a bug is more effective strategy compared to adding a random developer. You will will know if: * it's a regression or not * which code change caused the problem * which developer you have to contact It's a commit from Dennis Francis. He is already aware.. and assigned himself (<a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Wrong calculation after copy/paste of a formula" href="show_bug.cgi?id=132451">bug 132451</a>). Bibisecting is rather easy thing to do, and helpful: <a href="https://wiki.documentfoundation.org/QA/Bibisect">https://wiki.documentfoundation.org/QA/Bibisect</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>