<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Rename "kde5" VCL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125922#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Rename "kde5" VCL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125922">bug 125922</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>(In reply to Michael Weghorn from <a href="show_bug.cgi?id=125922#c7">comment #7</a>) > 'git blame' should be no problem, since 'git help blame' says: "The origin > of lines is automatically followed across whole-file renames (currently > there is no option to turn the rename-following off)." Ah nice. Missed that. So we would need an explicit rename commit without further changes in the source and git could handle that transparently. Normally you rename the file and change all the class stuff in one go, so that's probably why I had the impression that everything was treated as a deleted + new file instead of a rename. So no problem, if done right.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>