Date: Mon, 04 Jan 2021 16:58:40 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Kennedy <warlock@phouka.net> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: git non-time-sequential logs Message-ID: <94447.1609779520@critter.freebsd.dk> In-Reply-To: <X/NH3cb5eeweRibn@phouka1.phouka.net> References: <X/NA4Jk/P%2Bih5WSD@phouka1.phouka.net> <X/NH3cb5eeweRibn@phouka1.phouka.net>
index | next in thread | previous in thread | raw e-mail
-------- John Kennedy writes: > This might be perfectly natural and just new to me, but when I look at the > git logs this morning I see things like this (editing by me): > > Date: Mon Jan 4 17:30:00 2021 +0100 > Date: Mon Dec 14 18:56:56 2020 +0100 > Date: Tue Dec 15 13:50:00 2020 +0100 > Date: Mon Jan 4 16:23:10 2021 +0100 > > I've always assumed that the "Date:" there was when the commit happened, It is, but it is the time it was committed in the first git repos it was committed to, in this case the repos of the committer in question. Without taking a position on the merits of this design-choice, I just want to point out that it means that timestamps should be viewed very sceptically, since they depend on the *local* clock on somebodys computer, not on the central repos machine. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94447.1609779520>