On February 21, 2018 6:13 PM, Peter Backes wrote: > On Wed, Feb 21, 2018 at 11:44:13PM +0100, Ævar Arnfjörð Bjarmason wrote: > > If it were added as a first-level feature to git it would present a > > lot of UX confusion. E.g. you run "git add" and it'll be showing the > > mtime somehow, or you get a formatted patch over E-Mail and it doesn't > > only include the commit time but also times for individual files. > > But that's pretty standard. patch format has timestamp fields for precisely > this purpose: > > % echo a > x > % echo b > y > % diff -u x y > --- x 2018-02-21 23:56:29.574029523 +0100 > +++ y 2018-02-21 23:56:31.430003389 +0100 May I suggest storing the date/time in UTC+0 in all cases. I can see potential issues a couple of times a year where holes exist. I cannot even fathom what would happen on a merge or edit of history. Cheers, Randall
