From: <flzdjhmtax@wylie.me.uk> (Alan J. Wylie)
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [RESOLVED] Change History of linux commands
Date: Fri, 07 Oct 2022 19:27:36 +0100 [thread overview]
Message-ID: <87czb378ll.fsf@wylie.me.uk> (raw)
In-Reply-To: <f24d2464-2db0-8035-824e-d6977e1a3835@web.de> (n952162@web.de's message of "Fri, 7 Oct 2022 16:29:18 +0200")
(resending with correct From: address)
n952162 <n952162@web.de> writes:
> Am 07.10.22 um 16:25 schrieb n952162:
>> Can anybody tell me how I can look at the official change history of
>> linux commands?
>>
>> For example, the test(1) command used to have a regular-expression
>> parser built in. No longer, and more surprising, there's no discussion
>> of its disappearance on the internet; that I can find, at any rate.
>>
>> I'd to know when it disappeared and what discussions, by whom, preceded
>> that.
> Sorry, I'm thinking of the expr(1) command.
The man pages (and source code) of old versions of UNIX can be found at
https://minnie.tuhs.org/cgi-bin/utree.pl
e.g. ("man 1 expr" from Jan 1992)
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V10/man/man1/expr.1
For more human readable output
$ cd tmp
$ cat > oldman.1
<copy and paste>
$ man ./oldman.1
--
Alan J. Wylie https://www.wylie.me.uk/
Dance like no-one's watching. / Encrypt like everyone is.
Security is inversely proportional to convenience
next prev parent reply other threads:[~2022-10-07 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:25 [gentoo-user] Change History of linux commands n952162
2022-10-07 14:29 ` [gentoo-user] [RESOLVED] " n952162
2022-10-07 18:27 ` Alan J. Wylie [this message]
2022-10-07 14:56 ` [gentoo-user] " Grant Taylor
2022-10-07 15:25 ` n952162
2022-10-07 15:47 ` tastytea
2022-10-07 15:55 ` n952162
2022-10-07 15:57 ` Michael Orlitzky
2022-10-07 15:57 ` Laurence Perkins
2022-10-07 16:31 ` Matt Connell
2022-10-07 17:04 ` Grant Taylor
2022-10-07 17:10 ` Matt Connell
2022-10-07 17:39 ` Grant Taylor
2022-10-07 17:24 ` Dale
2022-10-09 15:59 ` Róbert Čerňanský
2022-10-07 16:23 ` Philip Webb
2022-10-07 17:07 ` Grant Taylor
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=87czb378ll.fsf@wylie.me.uk \
--to=flzdjhmtax@wylie.me.uk \
--cc=gentoo-user@lists.gentoo.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