On Mon, 20 Jun 2016 15:39:28 -0400, Jeff King wrote: > On Mon, Jun 20, 2016 at 12:05:07PM -0700, Norbert Kiesel wrote: > > > Hmm. On closer inspection that commit 23c07cc that github shows with > > date 2152-06-19 is already in my local branch. I got confused because > > locally it is shown with a different date: `git log -1 --format='%ci' > > 23c07cc` shows "2106-02-07 06:28:56 -40643156" which is invalid. > > > > My system is running Debian unstable 64bit. Is git using the time > > rendering methods from the C library (glibc 2.22-12)? > > No, git's time code is (mostly) internal routines. Can you show us the > output of: > > git cat-file commit 23c07cc | egrep '^author|committer' > > Note also that some interfaces (like "git log", and GitHub) will show > the author date by default, which might be different than the committer > date. The "-40643156" timezone definitely looks suspicious, though. I'm > curious if it is bad handling in the time code, or if the commit has > corrupt ident lines. > > -Peff 2106 is the year of unsigned 32-bit unix time bug, would there be any relation ? -- Eric Deplagne
Attachment:
signature.asc
Description: Digital signature