so i messed this up once and was gonna re-do it all but then i decided “… you know what this would be interesting to film”
for those of you who don’t know: Git does not distinguish between negative-0 and positive-0 offsets. but to pay homage to RFC 2822’s convention to use +0000 to represent a real timezone while -0000 to represent the lack of time zone i decided to re-write all commits i made on the VPS with -0000.
so to fix that minor slip-up i had to modify the rebase instruction format to do a crude find-and-replace of +0000 (i have never been anywhere near that European zone so any appearance of it must indicate a lack of timezone) in the commit object, then re-write it. but i should not touch the other branch that comes from upstream, since those are made by people much less pedantic than me and, in fact, use +0000 a lot. so git rebase wouldn’t cut it… and here we are.
(well, technically after that one big merge and the commits are all mine, i could technically do a git rebase -i <base> --rebase-merges of everything from there… but c’mon where’s the fun in that. besides, not every branch has to be rebased - just the direct descendants of the affected commit! :)
oh, and the rebase instruction is this by the way. don’t use it if you have +0000 in your commit message or your author/committer name, by the way – it’s not smart enough to distinguish those cases…