Thus said Richard Hipp on Wed, 25 Feb 2015 10:04:54 -0500: > The dates on timelines (the YYYY-MM-DD) could be seen as being in the > wrong place. The dates are positioned at a point on the timeline where > the HH:MM:SS for the date is 23:59:59.999. But since the HH:MM:SS is > not shown, that implies it is 00:00:00.
I currently see this in a test repository: 2015-02-26 04:42 04:40 04:37 Are you suggesting instead that this should be: 04:42 04:40 04:37 2015-02-26 If not, I suppose I'm having a hard time picturing what is wrong with the timeline. If so, then changing would certainly throw off those who have become accostomed to it being this way, however, would it be better for new Fossil users who have never seen the UI? Perhaps change it in a branch and let us experiment to see how much it interrupts our interpretation of the timeline? We may find that it is more natural to have the date displayed at the top of all the commits for that date, rather than in the correct chronological order---I suspect that is why (almost?) nobody has complained about it in 8 years. Thanks, Andy -- TAI64 timestamp: 4000000054eea610 _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev