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 18:05:45 -0700 [thread overview]
Message-ID: <426D93E9.10407@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504251756190.18901@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 25 Apr 2005, H. Peter Anvin wrote:
>
>>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.
>
> You have a different definition of "trivial" than I do. I have not a
> frigging clue how to handle leap seconds etc ;)
>
Leap seconds don't exist in the POSIX time_t universe, so they always obey:
... + 3600*hour + 60*min + sec
... which means that during a positive leap second, time_t remains
unchanged for 2 seconds, and for a negative leap second time_t jumps.
Thus, the difference between two time_t doesn't always match the exact
number of seconds between those two points in time.
>
>> And again, curl_gettime() does handle the whole string to time_t
>>conversion of the common formats.
>
> I don't doubt you, I just would prefer to not rely on boutique libraries
> too much.
>
> Yeah, we already use it for http-pull, so I guess it's moot, but at least
> that felt less like a core command..
>
If we're already using libcurl, we might as well. Otherwise, I'd just
rip out curl_gettime from the libcurl sources.
-hpa
prev parent reply other threads:[~2005-04-26 1:01 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
2005-04-26 0:58 ` Linus Torvalds
2005-04-26 1:05 ` H. Peter Anvin [this message]
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=426D93E9.10407@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).