The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ken Thompson <kenbob@gmail.com>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: When did "man cal" lose the comment about 1752?
Date: Mon, 15 Jul 2024 12:04:40 -0700	[thread overview]
Message-ID: <CAMP=X_mOeTPPQLi61aEc2+kt=S2SFrD6CVfxGNH1uz6b3HTe4A@mail.gmail.com> (raw)
In-Reply-To: <CAMP=X_mSh7-E8QySEW96n-S6o_Hfd2bQDLOFe-oO7bQQeYgJbg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

it is worse than "per country",
alaska changed when the u.s.
bought it from russia.

On Mon, Jul 15, 2024 at 12:03 PM Ken Thompson <kenbob@gmail.com> wrote:

> it is worse than "per country",
> alaska changed when the u.s.
> bought it from russia.
>
>
> On Mon, Jul 15, 2024 at 10:45 AM Greg A. Woods <woods@robohack.ca> wrote:
>
>> At Sun, 14 Jul 2024 17:15:53 -0400, Marc Donner <marc.donner@gmail.com>
>> wrote:
>> Subject: [TUHS] Re: When did "man cal" lose the comment about 1752?
>> >
>> > My instance of cal (MacOS 14.5) has this in the man page:
>> >
>> >      -s country_code
>> >
>> >              Assume the switch from Julian to Gregorian Calendar at the
>> date
>> >              associated with the country_code.  If not specified, ncal
>> tries
>> >              to guess the switch date from the local environment or
>> falls back
>> >              to September 2, 1752.  This was when Great Britain and her
>> >              colonies switched to the Gregorian Calendar.
>>
>> That's 'ncal' from FreeBSD, which is an entirely "new" implementation
>> written by Wolfgang Helbig:
>>
>>         commit 0cb2e609d9c2f0ceaf730a57ac5c11580058e7f4
>>         Author: Wolfgang Helbig <helbig@FreeBSD.org>
>>         Date:   Mon Dec 15 20:35:22 1997 +0000
>>
>>             Add new command ncal.
>>
>> > Note that the switch to the Gregorian calendar happened at different
>> times
>> > in different countries.  In Catholic-dominated countries it happened in
>> > October of 1582.  The English-speaking world, being
>> Protestant-dominated,
>> > waited until September of 1752 to adopt it.
>>
>> Indeed!
>>
>> --
>>                                         Greg A. Woods <gwoods@acm.org>
>>
>> Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
>> Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>
>>
>

[-- Attachment #2: Type: text/html, Size: 3658 bytes --]

  reply	other threads:[~2024-07-15 19:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  1:24 [TUHS] " Dave Horsfall
2024-07-11  1:44 ` [TUHS] " Greg 'groggy' Lehey
2024-07-11  3:10   ` Dave Horsfall
2024-07-11 19:31   ` Stuff Received
2024-07-11  1:53 ` Henry Bent
2024-07-11  3:29   ` Dave Horsfall
2024-07-14 19:04   ` Greg A. Woods
2024-07-14 21:15 ` Marc Donner
2024-07-15 14:00   ` Paul Winalski
2024-07-15 18:21     ` Marc Donner
2024-07-15 18:41       ` Phil Budne
2024-07-15 17:44   ` Greg A. Woods
2024-07-15 19:03     ` Ken Thompson
2024-07-15 19:04       ` Ken Thompson [this message]
2024-07-15 20:02         ` Jaap Akkerhuis via TUHS
2024-07-15 19:33       ` Marc Donner
2024-07-16 15:54         ` Paul Winalski
2024-07-11  4:20 Rudi Blom
2024-07-15 19:52 [TUHS] " Douglas McIlroy
2024-07-16  6:59 ` [TUHS] " markus schnalke
2024-07-16 20:22   ` Steffen Nurpmeso
2024-07-16 21:21     ` segaloco via TUHS

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='CAMP=X_mOeTPPQLi61aEc2+kt=S2SFrD6CVfxGNH1uz6b3HTe4A@mail.gmail.com' \
    --to=kenbob@gmail.com \
    --cc=tuhs@tuhs.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).