Re: [fossil-users] Timestamps should be in local time.
On Sat, 20 Aug 2011, Vikrant Chaudhary wrote: Timestamps should be recorded in local timezone rather than in UTC. 1. It hurts eyes and brain to see the time in UTC and then calculate it in local time. 2. For forensics. I'll be able to know which timezone I was while committing that change. And we can always calculate the UTC time anyway. And by storing the time in local time we'll only gain the timezone information in history and loose nothing. Re: 1) as others have pointed out: this is configurable through the UI. Re: 2) If there is a convincing use case for your proposal I would store the time stamp in UTC and store the time zone separately (offset in minutes from UTC). Currently fossil can just use an SQL 'ORDER BY' clause to retrieve commits etc. in order, using local time stamps would make that more painful and definitly slower (you cannot create a simple index for that) Gé ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Timestamps should be in local time.
I assume if I de-select UTC, fossil will still use UTC in the database but show local time zone on timeline. Correct? - Original Message - From: Gé Weijers Sent: 08/21/11 09:36 PM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Timestamps should be in local time. On Sat, 20 Aug 2011, Vikrant Chaudhary wrote: Timestamps should be recorded in local timezone rather than in UTC. 1. It hurts eyes and brain to see the time in UTC and then calculate it in local time. 2. For forensics. I'll be able to know which timezone I was while committing that change. And we can always calculate the UTC time anyway. And by storing the time in local time we'll only gain the timezone information in history and loose nothing. Re: 1) as others have pointed out: this is configurable through the UI. Re: 2) If there is a convincing use case for your proposal I would store the time stamp in UTC and store the time zone separately (offset in minutes from UTC). Currently fossil can just use an SQL 'ORDER BY' clause to retrieve commits etc. in order, using local time stamps would make that more painful and definitly slower (you cannot create a simple index for that) Gé ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Timestamps should be in local time.
This is a setting. Admin-Timeline Display Settings Use Universal Coordinated Time (UTC) On Sat, Aug 20, 2011 at 10:46 AM, Vikrant Chaudhary nas...@gmail.com wrote: Timestamps should be recorded in local timezone rather than in UTC. 1. It hurts eyes and brain to see the time in UTC and then calculate it in local time. 2. For forensics. I'll be able to know which timezone I was while committing that change. And we can always calculate the UTC time anyway. And by storing the time in local time we'll only gain the timezone information in history and loose nothing. -- -nasa http://vikrant.co.in/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Timestamps should be in local time.
On 8/20/2011 10:46 AM, Vikrant Chaudhary wrote: Timestamps should be recorded in local timezone rather than in UTC. 1. It hurts eyes and brain to see the time in UTC and then calculate it in local time. The timestamps in the timeline can be configured to be shown in local time via the web ui: Admin Timeline Use Universal Coordinated Time (UTC). If there's anywhere else that UTC is used and one can't choose the local time view instead, I'd call that a missing feature. 2. For forensics. I'll be able to know which timezone I was while committing that change. But I believe you're asking for time zone information to be stored along with commits so that, e.g., the timeline could show a mix of timezones. I'm a little confused as to when you would not be able to establish where in the world you were for a commit, e.g., by your calendar combined with the date and time. If you routinely switch timezones during the course of a day *and* routinely need to know which you were in when you made a commit, I could see it becoming inconvenient, but I submit that this is probably a *very* fringe use. And if you did this often, you either switch your laptop's timezone a couple times a day, or else you're using different machines, in which case you could just create another fossil user for yourself and associate it with the other machine. And we can always calculate the UTC time anyway. And by storing the time in local time we'll only gain the timezone information in history and loose nothing. If this were determined to be worth doing, it would probably better to keep the storage in UTC so that the DB could readily compare the dates and also store the local timezone at commit time. But I really don't see it. I can see someone wanting the timeline in their own time zone. I can see a distributed team standardizing on UTC so everyone sees the same thing. But it's confusing to show times from more than one zone in the same view. I don't see many people wanting that. -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
