>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1067500. --> Reported by: [anarcat](https://www.drupal.org/user/1274) >>> <p>As documented in <a href="http://groups.drupal.org/node/128479">this thread</a> we have been lucky enough to migrate to git before everybody else here, so the migration back to git for us is just a matter of doing a git clone, no need to convert from CVS. sdboyer already took care of that <a href="https://github.com/sdboyer/drupalorg-git/commit/4c410d7c7e7f1c20b8586bf8441d24bec8bb6882">here</a> but since we're going to do the switch, which will rewrite part of the history to match commit authorship anyways, we figure we might as well use that opportunity to cleanup all of our historical commits.</p> <p>I was just chatting with sdboyer about this and he said it was okay to go ahead with this, and asked me to open this issue. :)</p> <p>Our problem is that we have a quite messy history:</p> <pre>hostmaster$ git rev-list --all --format='%an &lt;%ae&gt;' | grep -v '^commit'| sort -u | wc -l<br>28<br>provision$ git rev-list --all --format='%an &lt;%ae&gt;' | grep -v '^commit'| sort -u | wc -l<br>22</pre><p>... whereas in fact there are 10 authors in provision and 11 (maybe 12 or 13) in hostmaster. The reason why those listings pick up more is that there is a variety of authors emails and names in this history. A few problematic examples:</p> <pre>hostmaster$ git rev-list --all --format='%an &lt;%ae&gt;' | grep -v '^commit'| sort | uniq -c<br>&nbsp;&nbsp;&nbsp; 305 anarcat &lt;anarcat&gt;<br>&nbsp;&nbsp;&nbsp; 134 anarcat &lt;anarcat@koumbit.org&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp; 10 Antoine Beaupre &lt;anarcat@ceres.koumbit.net&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp; 11 Antoine Beaupre &lt;anarcat@hostmaster.koumbit.net&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp; 18 Antoine Beaupre &lt;anarcat@koumbit.org&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2 Antoine Beaupr&eacute; &lt;anarcat@koumbit.org&gt;</pre><p>The first is from our original CVS migration. The second is a misconfigured "real name" part. The third and fourth are misconfigured emails for hotfixes I did in production and testing. The fifth is without the accent and the last one is the right one, although it seems to be the least used one.</p> <p>Another type of issues:</p> <pre>hostmaster$ git rev-list --all --format='%an &lt;%ae&gt;' | grep -v '^commit'| sort | uniq -c<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 aegir &lt;aegir@gambit.greenbeedigital.com.au&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 aegir &lt;aegir@li94-211.members.linode.com&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2 Miguel Jacq &lt;miguel@crunchbang.(none)&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp; 78 Neil Drumm &lt;drumm@drumm-x200.(none)&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6 root &lt;root@r11567.ovh.net&gt;</pre><p>The first two we have no freaking clue who they are. Since it's only two commits: though luck, we'll just ignore that, I guess. But the next two are more problematic: they're not actually valid email addresses (yay OSX...) And the last one is a bit like the two first ones.</p> <p>Now I understand it's not your job to take care of cleaning up our messy repo. Maybe we can do a pass on our own before the final migration to clean it up first, in which case we would just need to sync with the final migration. But if you're going to remap the commit authors anyways, maybe this could all be done at the same time? Anything we need to do for this? I could provide mapping for the accounts I know of, for example...</p> <p>One thing I want to experiment with too is to understand what will be the effect of rewriting the history like this - if we need to reclone from scratch, that could be problematic. I was told by sdboyer that this could be worked around by git-rebase(1), as it could figure out those are only metadata changes and ditch the old commits... I guess only testing will tell there!</p> <p>Thank you for your amazing work on this epic migration!</p>