bad commit makes this repo un-pushable

[AArnott]

There's a bad commit in the history of this git repo. It prevents pushing this repo to GitHub or visualstudio.com.

git fsck fails:

git fsck
Checking object directories: 100% (256/256), done.
error in commit c1eddff4ee3f62b6039f1083651b9118883e7f07: badTimezone: invalid author/committer line - bad time zone
Checking objects: 100% (42066/42066), done.

Pushing to visualstudio.com fails:

git push vsts develop
Counting objects: 40380, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (13249/13249), done.
Writing objects: 100% (40380/40380), 17.91 MiB | 908.00 KiB/s, done.
Total 40380 (delta 27056), reused 40380 (delta 27056)
error: unpack failed: error The commit object c1eddff4ee3f62b6039f1083651b9118883e7f07 was rejected: Commit parse failed due to author identity failed to parse: Dan Loewenherz <dloewenherz@gmail.com> 1288373970 --700
To https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/boto
! [remote rejected] develop -> develop (The commit object c1eddff4ee3f62b6039f1083651b9118883e7f07 was rejected: Commit parse failed due to author identity failed to parse: Dan Loewenherz <dloewenherz@gmail.com> 1288373970 --700)
error: failed to push some refs to 'https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/boto'

Pushing to github fails:

git push github-test origin/master:refs/heads/master -f
Counting objects: 40423, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (13276/13276), done.
error: fatal: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053
The remote end hung up unexpectedly
Writing objects: 100% (40423/40423), 17.47 MiB | 430.00 KiB/s, done.
Total 40423 (delta 27072), reused 40423 (delta 27072)
fatal: The remote end hung up unexpectedly
Everything up-to-date

Fixing this probably means rewriting that commit and thus rewriting all history since then, which would be disruptive. But not being able to fork this repo (except perhaps by way of GitHub's built-in fork button) is also disruptive.

Can anything be done to fix this?

[AArnott]

Dupe of #3507

[AArnott]

Dupe of #3507