Am 30.12.18 um 03:48 schrieb Vagrant Cascadian:
> The problem with dates from git commits is that git makes no attempt to
> keep commits in cronological order, and timezone adds interesting issues
> to the mix. For example:

Though *author* dates might not be in cronological order, *commit* dates
are (as long as none is playing with the graph), see below.

Anyway, we are interested in the *commit*-date, thus git need to be told
do show this one:

$ git log -n 1 --format=format:"%h %ci"
402c36c1d 2018-12-30 17:05:27 -0500


$git log -n 5 --format=format:"Author:    %ai %an%nCommitter: %ci
%cn%n%n" c180017b6f7e9b6d23238c1fbaac986c435cd35e

Author:    2018-12-25 16:29:12 +0200 Efraim Flashner
Committer: 2018-12-27 14:55:54 +0200 Efraim Flashner
Author:    2018-11-20 17:46:24 +0100 Pierre-Antoine Rouby
Committer: 2018-12-27 12:08:25 +0100 Ludovic Courtès
Author:    2018-12-27 11:54:55 +0100 Ludovic Courtès
Committer: 2018-12-27 12:08:25 +0100 Ludovic Courtès
Author:    2018-12-27 11:53:14 +0100 Ludovic Courtès
Committer: 2018-12-27 12:08:25 +0100 Ludovic Courtès
Author:    2018-12-27 09:46:40 +0100 Julien Lepiller
Committer: 2018-12-27 09:47:22 +0100 Julien Lepiller


-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: https://www.goe-con.de/blog/35.000-gegen-vorratdatenspeicherung
Kolumne:
https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2010-09-mut-zur-beschraenkung