4 ms·
Another issue is that when you travel to a different timezone, you don't necessarily update the timezone of your system.
by glandium 7y ago
Another issue is that when you travel to a different timezone, you don't necessarily update the timezone of your system.
- cptskippy 7y agoAren't most devices configured to adjust automatically these days?
- mattlondon 7y agoI personally don't travel with my desktop :) Generally I take a small light laptop when traveling, and then just connect to the desktop back home for doing real work such as committing code. I know that at a lot of Big Cos do not let their engineers to have source code on laptops anyway (so easily lost and stolen).
- inlined 7y agoAt least Google has made an exception for me when I’m working on code hosted on Github. Most of that is (or will be) public so there’s low risk.
- glandium 7y agoNeither my Linux nor Windows 10 laptops do.
- Kye 7y agoBoth can be configured to do this, but I'm not sure it's enabled by default.
- franciscop 7y agoIn the blog post it specifies that it uses the Unix timestamp, which doesn't account for timezones.
- donatj 7y agoIt's Unix timestamp followed by timezone.
- cptskippy 7y agoYes and that's most irrelevant because we were discussing the device offset as users travel between timezones. Unix Timestamps are always expressed as UTC/TUC which remain constant regardless of device offsets. The origianl comment's assertion that users don't typically adjust their offsets is moot since commits are stored in UTC anyways. I was just pointing out that many devices automatically adjust offsets.