On 4/18/2023 12:12 AM, Jeff King wrote: > One thing the commit graph perhaps _could_ do is omit the commit, or > mark it as "this one is broken in some way". And then fall back to > parsing those few instead (which is slower, but if it's a small minority > of commits, that's OK). But I don't think there's any code for that. The "broken" commit would need to be included in the commit-graph file so its children can point to it using a graph position, but then it would revert to parsing from the commit object (due to some new concept storing "this is a bad commit"). If we decided to treat a timestamp of 0 as "probably broken, artificial at best" then we wouldn't need the new indicator in the commit-graph file, but this seems like quite a big hammer for a small case. Thanks, -Stolee
