Comment by kentonv

6 days ago

That's weird! It must be due to a history rewrite I did later on to clean up the repo, removing some files that weren't really part of the project. I didn't realize when I first started the experiment that we'd actually end up releasing the code so I had to go back and clean it up later. I am surprised though that this messed up the timestamps -- usually rebases retain timestamps. I think I used `git filter-branch`, though. Maybe that doesn't retain timestamps.

1 comment

kentonv

euiq 6 days ago

I know that `git rebase` changes the committer date while keeping the author date the same, so I'm assuming something similar happened here. For example, many of the early commits have this committer date with varying author dates:

    $ git show --format=fuller 3dafc8f5de6ffe46fb223a75a46a6bd848b6daf8
    commit 3dafc8f5de6ffe46fb223a75a46a6bd848b6daf8
    Author:     Kenton Varda <kenton@cloudflare.com>
    AuthorDate: Thu Feb 27 17:15:37 2025 -0600
    Commit:     Kenton Varda <kenton@cloudflare.com>
    CommitDate: Tue Mar 4 14:48:59 2025 -0600
    
        Add storage schema by Claude.

GitHub uses the committer date for its history, which is annoying if you rebase frequently; I like to run a non-interactive `git rebase` with `--commmiter-date-is-author-date` in such cases.