From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: git.git object database at kernel.org?
Date: Mon, 25 Apr 2005 17:48:31 -0700 [thread overview]
Message-ID: <426D8FDF.5050608@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504251729080.18901@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 25 Apr 2005, H. Peter Anvin wrote:
>
>>No, mktime() always uses the local time zone. It's the inverse of
>>localtime().
>
> Note that this still doesn't make any sense.
>
> A true inverse of "localtime()" should still take the GMT offset from
> "struct tm", and it would work fine, assuming that localtime() set that
> offset correctly.
>
> So _I_ think it's incredibly stupid that mktime() looks at the local
> timezone.
>
> Oh, well. Not a big issue except for the date conversion, and since there
> hopefully aren't any old repo's left, we can leave it behind us.
>
It *is* incredibly stupid, but dates back to the fact that a the GMT
offset field in struct tm is a reasonably recent invention, and a lot of
old code depended on just stuffing fields in struct tm and calling
mktime(); they would leave the offset field uninitialized, as opposed to
setting it to some well-defined "I don't know" value.
What totally blows is that if mktime() can't be fixed, that we haven't
added mktime_have_offset() or something like that.
Oh well. If you have the offset, the algorithm is fully arithmetric and
doesn't rely on the zoneinfo system, so it can be trivially implemented.
And again, curl_gettime() does handle the whole string to time_t
conversion of the common formats.
-hpa
next prev parent reply other threads:[~2005-04-26 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7vhdhvstb2.fsf@assigned-by-dhcp.cox.net>
2005-04-24 23:08 ` git.git object database at kernel.org? Linus Torvalds
2005-04-25 18:46 ` H. Peter Anvin
2005-04-25 19:05 ` H. Peter Anvin
2005-04-26 0:32 ` Linus Torvalds
2005-04-26 0:48 ` H. Peter Anvin [this message]
2005-04-26 0:58 ` Linus Torvalds
2005-04-26 1:05 ` H. Peter Anvin
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=426D8FDF.5050608@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).