Re: Mechanism to provide tai-utc.dat locally
This message
: [
Message body
] [ More options (
top
,
bottom
) ]
Related messages
: [
Next message
] [
Previous message
] [
In reply to
] [
Next in thread
]
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]
From
: Ashley Yakeley <
ashley_at_SEMANTIC.ORG
>
Date
: Mon, 25 Dec 2006 22:41:31 -0800
On Dec 25, 2006, at 04:46, Zefram wrote:
> The table at <
ftp://time.nist.gov/pub/leap-seconds.list
> has an
> explicit
> expiry date. (I'm going to make Time::UTC use this at some point.)
I agree this is better because of the expiry date.
This is a bit faster: <
ftp://time-b.nist.gov/pub/leap-seconds.list
>
Some other files I've found:
<
ftp://oceans.gsfc.nasa.gov/COMMON/leapsec.dat
>
<
ftp://oceans.gsfc.nasa.gov/COMMON/utcpole.dat
>
-- Ashley Yakeley
Received on
Mon Dec 25 2006 - 22:41:53 PST
This message
: [
Message body
]
Next message
:
Rob Seaman: "Re: [LEAPSECS] Mechanism to provide tai-utc.dat locally"
Previous message
:
Zefram: "Re: [LEAPSECS] Mechanism to provide tai-utc.dat locally"
In reply to
:
Zefram: "Re: [LEAPSECS] Mechanism to provide tai-utc.dat locally"
Next in thread
:
Ed Davies: "Re: [LEAPSECS] Mechanism to provide tai-utc.dat locally"
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]
This archive was generated by
hypermail 2.3.0
: Sat Sep 04 2010 - 09:44:55 PDT