Re: Weird behavior of 'git log --before' or 'git log --date-order': Commits from 2011 are treated to be before 1980

From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Apr 17, 2023, 06:20 UTC
Message-ID: <b517d7ca-4b8f-487b-8836-8966a2a9d9ee@app.fastmail.com>
In-Reply-To: <20230417054032.GA26997@coredump.intra.peff.net>

On Mon, Apr 17, 2023, at 07:40, Jeff King wrote:

> I don't know if git-repair will fix syntactic problems in commits like
> this, or if it's just looking for broken links between objects. But
> regardless, it would be possible to fix these using filter-repo or other
> tools.

Makes sense, thanks.

I gave up since the program never seemed to finish.

> The problem with repairing them is that it rewrites history, changing
> the object id of every commit which comes after.  So you'd want to do it
> once centrally for the project, and declare a flag day that everybody is
> moving over to the new, fixed history.

I wasn’t interested in fixing the repo for future development. Just to see if that weird git-log(1) behavior went away. It’s like the inverse of a minimal example to reproduce a bug; repair the corrupt object so that future askers can be convinced that it’s not a bug. ;)

I’m not affiliated with the project.

-- 
Kristoffer Haugsbakk