public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sergio at sergiomb dot no-ip dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4033] mktime bug in Europe/Lisbon timezone Date: Sat, 17 Feb 2007 16:44:00 -0000 [thread overview] Message-ID: <20070217164416.9871.qmail@sourceware.org> (raw) In-Reply-To: <20070213141801.4033.cvalente@spambob.com> ------- Additional Comments From sergio at sergiomb dot no-ip dot org 2007-02-17 16:44 ------- (In reply to comment #3) > There is nothing wrong here. This is the daylight saving time switch. The > mktime is intelligent in that it gives an answer based on the context which is > more correct than always returning the old or new time. what context ? >>> import time >>> time.mktime((1976,9,26,0,0,0,0,0,0)) 212544000.0 >>> time.mktime((1976,9,25,0,0,0,0,0,0)) 212454000.0 >>> time.mktime((1976,9,26,0,0,0,0,0,0)) 212540400.0 I just want to know how I convert strtotime and after timetostr and get the same initial string, if it a valid string date. I do this to validate the strings. I verified that 01-jan-1970 after strtotime and timetostring give me 31-dez-1969 23.00 which I think this is not correct ! -- http://sourceware.org/bugzilla/show_bug.cgi?id=4033 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2007-02-17 16:44 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-13 14:18 [Bug libc/4033] New: " cvalente at spambob dot com 2007-02-13 14:19 ` [Bug libc/4033] " cvalente at spambob dot com 2007-02-13 14:24 ` sergio at sergiomb dot no-ip dot org 2007-02-17 6:43 ` drepper at redhat dot com 2007-02-17 16:44 ` sergio at sergiomb dot no-ip dot org [this message] 2007-02-21 19:13 ` sergio at sergiomb dot no-ip dot org 2007-02-21 19:16 ` drepper at redhat dot com 2007-02-22 5:20 ` sergio at sergiomb dot no-ip dot org 2007-02-22 5:26 ` sergio at sergiomb dot no-ip dot org 2007-02-22 5:29 ` sergio at sergiomb dot no-ip dot org 2007-02-22 6:06 ` drepper at redhat dot com 2007-02-22 15:04 ` sergio at sergiomb dot no-ip dot org 2007-02-22 15:17 ` drepper at redhat dot com 2007-02-22 15:52 ` jakub at redhat dot com 2007-03-30 13:26 ` sergio at sergiomb dot no-ip dot org 2007-03-30 14:19 ` drepper at redhat dot com 2007-03-30 14:47 ` sergio at sergiomb dot no-ip dot org 2007-03-30 14:50 ` drepper at redhat dot com 2008-02-15 17:31 ` sergio at sergiomb dot no-ip dot org 2008-03-05 2:52 ` sergio at sergiomb dot no-ip dot org 2008-03-29 3:22 ` sergio at sergiomb dot no-ip dot org
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=20070217164416.9871.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).