From: Jan Harkes <jaharkes@cs.cmu.edu>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: Date handling.
Date: Sun, 24 Apr 2005 21:22:23 -0400 [thread overview]
Message-ID: <20050425012216.GH29939@delft.aura.cs.cmu.edu> (raw)
In-Reply-To: <1114324729.3419.78.camel@localhost.localdomain>
On Sun, Apr 24, 2005 at 04:38:49PM +1000, David Woodhouse wrote:
> On Sat, 2005-04-23 at 23:04 -0400, Jan Harkes wrote:
> > I noticed that some commit timestamps seemed to be off, looking into it
> > a bit more it seems like mktime is influenced by the setting of the
> > local TZ environment.
>
> Ewww. I missed that in the documentation. I suppose I should have worked
> it out having empirically determined that it ignores the tm_gmtoff
> field.
>
> > The question is, do we want to just calculate the time_t offset
> > ourselves without using mktime, or force the TZ environment to UTC.
>
> I don't think we want to be in the business of counting leap seconds; we
> need to let the system do it. I don't much like setting TZ to UTC though
> -- how about we use your test case to find the offset and subtract that?
>
> Does this work?
As Russ mentioned, that probably doesn't work with daylight savings
time. However I did some testing and it looks like the following lines
around mktime make it work as we would expect.
tm.tm_isdst = -1;
then = mktime(&tm);
then += tm.tm_gmtoff;
Attached is the program I used to test it, it seems pretty much unfazed
by changes to the TZ environment variable. Although I tested around a
daylight savings time switch, I'm still not 100% sure if it doesn't mess
up in some corner case.
Jan
#include <time.h>
#include <stdlib.h>
#include <stdio.h>
time_t mkutctime(struct tm *tm, int offset)
{
time_t time;
/* we don't know whether our timezone happens to be dst or not, let libc
* figure that one out. */
tm->tm_isdst = -1;
/* interpret struct tm in the local timezone */
time = mktime(tm);
if (time == -1) return -1;
/* libc lets us know how many seconds our local time differs from UTC
* this is a non-standard BSD extension, which is probably not as
* portable, but it seems to work. */
time += tm->tm_gmtoff;
/* However as the passed in struct tm was not UTC but in some other
* timezone, we still have subtract the offset that came with the
* RFC2822 date */
time -= offset;
return time;
}
int main(int argc, char **argv)
{
struct tm tm = { 0, };
time_t time;
tm.tm_year = 70;
tm.tm_mday = 1;
time = mkutctime(&tm, 0);
printf("1970-01-01 00:00:00 UTC = 0 (%d)\n", time);
tm.tm_year = 105;
tm.tm_mon = 2;
tm.tm_mday = 17;
tm.tm_hour = 20;
tm.tm_min = 58;
tm.tm_sec = 31;
time = mkutctime(&tm, -5 * 3600);
printf("2005-03-17 20:58:31 EST = 1111111111 (%d)\n", time);
tm.tm_mon = 3;
tm.tm_mday = 3;
tm.tm_hour = 1;
tm.tm_min = 59;
tm.tm_sec = 59;
time = mkutctime(&tm, -5 * 3600);
printf("2005-04-03 01:59:59 EST = 1112511599 (%d)\n", time);
tm.tm_hour = 3;
tm.tm_min = 0;
tm.tm_sec = 0;
time = mkutctime(&tm, -4 * 3600);
printf("2005-04-03 03:00:00 EDT = 1112511600 (%d)\n", time);
}
next prev parent reply other threads:[~2005-04-25 1:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 8:16 Date handling David Woodhouse
2005-04-14 9:00 ` Linus Torvalds
2005-04-14 9:12 ` Linus Torvalds
2005-04-14 17:38 ` David Woodhouse
2005-04-14 19:19 ` tony.luck
2005-04-14 19:23 ` David Woodhouse
2005-04-24 3:04 ` Jan Harkes
2005-04-24 3:33 ` James Purser
2005-04-24 6:38 ` David Woodhouse
2005-04-24 6:43 ` Russ Allbery
2005-04-25 1:22 ` Jan Harkes [this message]
2005-04-25 1:32 ` Russ Allbery
2005-04-14 9:31 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 19:42 Luck, Tony
2005-04-14 20:54 ` David Woodhouse
2005-04-14 21:01 ` H. Peter Anvin
2005-04-14 21:48 ` David Woodhouse
2005-04-15 5:02 ` Paul Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050425012216.GH29939@delft.aura.cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).