The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: When did "man cal" lose the comment about 1752?
Date: Sun, 14 Jul 2024 12:04:44 -0700	[thread overview]
Message-ID: <m1sT4Wb-0036s2C@more.local> (raw)
In-Reply-To: <CAEdTPBf+Kg3v2dK8QXC-Kxe3fVmfGhJQ8oRfM1Lei13Y9suWBg@mail.gmail.com>

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

At Wed, 10 Jul 2024 21:53:54 -0400, Henry Bent <henry.r.bent@gmail.com> wrote:
Subject: [TUHS] Re: When did "man cal" lose the comment about 1752?
>
> Looks like on the BSD side it disappeared between 4.3 Tahoe and Reno.  It's
> in research through v10.  It's in SVR2; SVR4 modifies it to say "An unusual
> calendar is printed for September 1752."  I don't seem to have manpages
> with either of the SVR3 source distributions that I have handy.  So to
> answer your basic question, it stayed around for quite a while.

System V Release 3.2 MRD says the same thing as SVR4:

            An unusual calendar is printed for September 1752.  That is
            the month 11 days were skipped to make up for lack of leap
            year adjustments.  To see this calendar, type: "cal 9 1752"

The "BUGS" section remains the same as it was in 7th Edition.

In the CSRG SCCS files cal(1) was "updated" after the 4.3BSD release
with this comment:

src/usr.bin/cal/SCCS/s.cal.1
	D 6.3 89/09/28 14:20:22 bostic 5 4      00042/00023/00009
	MRs:
	COMMENTS:
	new version from Kim Letkeman (mitel!spock!kim@uunet.UU.NET)

The code was also updated at the same time:

src/usr.bin/cal/SCCS/s.cal.c
	D 4.5 89/09/28 14:20:24 bostic 5 4      00222/00159/00043
	MRs:
	COMMENTS:
	new version from Kim Letkeman (mitel!spock!kim@uunet.UU.NET)

This is of course a complete rewrite to give UCB the copyright.

--
					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: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-07-14 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 [this message]
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
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=m1sT4Wb-0036s2C@more.local \
    --to=woods@robohack.ca \
    --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).