>I'm trying to do an updated git export (in respect to the one Graydon >did updated to commits from 17 years ago), but there are a few "bad >date" commits with the following git hashes: > >% cat .git/skiplist >23b779f1005d828e0df269b436017758b8c610e6 >25ed9886faa93ded2e62d218745502bdd9162a2f >02742528fa884a5f8a52d1c0690d5a6f1f729f3e >7c4e0935f86719d2c80bb246a884e799c39c829d >7117412862fcfddc9ab1459e20a487e31da0f12e > >I tracked down the first one as this: > >Revision: 00bc6370f21302d2bd7f2008f4608d3a2d5683d0 >Author: Timothy Brownawell <[email protected]> >Date: 1969-12-21 02:50:07 >Branch: net.venge.monotone.tbrownaw.serve_automate > >For this reason I couldn't push on github (badDate: invalid >author/committer line - bad date), but I managed to push on my personal >ForgeJo > >https://git.lapo.it/lapo/monotone/ > >Maybe there's some way to force push on GitHub, assuming there's any >value in that.
I do have an export to GitHub; I suspect I have just dropped the 5 date certificates. >Or maybe `sed` away the dates during export. 🤔 > >-- >Lapo Luchini > >
