From: itz@very.loosely.org (Ian Zimmerman)
Subject: [TUHS] OT: trains [Was: Date madness]
Date: Mon, 18 Dec 2017 08:45:26 -0800 [thread overview]
Message-ID: <20171218164526.ptsvevdf4touatg6@matica.foolinux.mooo.com> (raw)
In-Reply-To: <1513602204.10161.for-standards-violators@oclsc.org>
On 2017-12-18 08:03, Norman Wilson wrote:
> Suppose I'm planning to board a train at 0300 on the morning
> Daylight Time ends.
>
> Now suppose the train actually departs an hour early, at 0200,
> because it originated before the time change and some nerd who
> never rides trains declared that it shall not wait the extra
> hour until scheduled departure time.
>
> Nerds may be happy, but the paying passengers won't be.
Yes, this was the problem I was asking about. Plus the even more vexing
problem of time discontinuity when the train is already en route.
I can still remember the days of thick bound paper schedules in Europe,
and I think for overnight routes there usually was a tiny footnote
about the 2 critical days. New book schedules were issued each year so
the footnotes could be specific about the dates. What I don't know is
how this transitioned into the digital age.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.
next prev parent reply other threads:[~2017-12-18 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 22:16 [TUHS] Date madness Norman Wilson
2017-12-14 0:24 ` Chris Torek
2017-12-17 16:20 ` Ron Natalie
2017-12-17 18:53 ` Tom Ivar Helbekkmo
2017-12-17 20:07 ` Ron Natalie
2017-12-17 21:24 ` [TUHS] OT: trains [Was: Date madness] Ian Zimmerman
2017-12-17 22:35 ` Dave Horsfall
2017-12-18 13:03 ` Norman Wilson
2017-12-18 16:45 ` Ian Zimmerman [this message]
2017-12-19 0:48 ` Dave Horsfall
2017-12-18 16:12 ` Steve Mynott
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=20171218164526.ptsvevdf4touatg6@matica.foolinux.mooo.com \
--to=itz@very.loosely.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).