<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That requires rewriting commit history all the way back to there. We won’t be doing that. You can make forks it our stash.<div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 24, 2017, at 12:15 PM, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" class="">s.safarov@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Could team developers fix multiple 'author' for commits 487128950df6ee433c131b5feaafe81ee86629f4 and 8574988c3a378b4d5861ecaeb0e958657635703b.<br class="">Without this to to difficult fork repo and late to track changes on GitHub<br class=""><div class=""><br class=""></div><p class="inbox-inbox-p1"><font face="monospace" class=""><span class="inbox-inbox-s1">home$ git fsck<br class=""></span>Checking object directories: 100% (256/256), done.<br class="">error in commit 487128950df6ee433c131b5feaafe81ee86629f4: multipleAuthors: invalid format - multiple 'author' lines<br class="">error in commit 8574988c3a378b4d5861ecaeb0e958657635703b: multipleAuthors: invalid format - multiple 'author' lines<br class="">Checking objects: 100% (306371/306371), done.</font></p><div class=""> </div></div></div></blockquote></div></div></body></html>