From: "H. Peter Anvin" <email@example.com>
Subject: Re: LSE conference call
Date: 3 May 2003 15:11:17 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Followup to: <email@example.com>
By author: firstname.lastname@example.org (Eric W. Biederman)
In newsgroup: linux.dev.kernel
> Scott Robert Ladd <email@example.com> writes:
> > John Bradford wrote:
> > > Ah, but assuming that you had a compass to calculate the local time
> > > offset, (ignoring DST), anyway, you could have used that to calculate
> > > the _local_ time without looking at your watch at all ;-). However,
> > > you wouldn't be able to calculate the timezone you were in.
> > Ah, but if you had a GPS system available, and a database of time zone
> > boundaries, you could adjust on-the-fly for different jurisdictions. I've dones
> > somethign of the sort recently for a client; the main problem lies in the
> > accuracy (and size) of the database. Indiana, for example, presents unique
> > challenges, with its patchwork implementation of DST...
> Indiana doesn't do DST. But it is true that people on the edges of the state
> like to know what time it is for their neighbors across the border.
Part of Indiana does DST, part of it doesn't. In particular, the
parts of Indiana is in the CT timezone (Gary area) *does* do DST.
<firstname.lastname@example.org> at work, <email@example.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
prev parent reply other threads:[~2003-05-03 21:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 17:44 LSE conference call John Bradford
2003-04-18 19:58 ` Cliff White
2003-04-18 22:08 ` William Lee Irwin III
2003-04-19 10:03 ` John Bradford
2003-04-22 17:43 ` Hanna Linder
2003-04-22 17:49 ` John Bradford
2003-04-23 1:13 ` jw schultz
2003-04-25 17:55 ` Bill Davidsen
2003-04-25 18:26 ` John Bradford
2003-05-02 15:33 ` Scott Robert Ladd
2003-05-03 14:17 ` Eric W. Biederman
2003-05-03 22:11 ` H. Peter Anvin [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).