(When I saw the title, I was wondering if this does something beyond the basic rebase, like trying to brute force a commit such that all following commits are preserved (hash doesn&#x27;t change), but that&#x27;s essentially impossible.)<p>I&#x27;m tempted to make the observation that there&#x27;s nothing here you can&#x27;t already do with a git rebase -i and:<p><pre><code>    GIT_COMMITTER_NAME=a GIT_COMMITTER_EMAIL=a@a.com GIT_COMMITTER_DATE=2006-01-02T15:04:05Z git commit --author=&#x27;a &lt;a@a.com&gt;&#x27; --date 2006-01-02T15:04:05Z
</code></pre>
But I realize this ability will be novel&#x2F;surprising to some people, and this is meant to be a joke.<p>I don&#x27;t do this not because I can&#x27;t, but because I have no incentive to lie about who wrote&#x2F;committed certain code.