The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Wed, 20 Sep 2023 16:12:26 +0200	[thread overview]
Message-ID: <CAJbEFzheZs-b4eS0OSi3s3kSc1jA3fhj+X5dOGNWQbT4+WXRQQ@mail.gmail.com> (raw)
In-Reply-To: <2c971548-14c1-420b-ba7b-5c2272da89b2@case.edu>

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

On Wed, Sep 20, 2023, 15:23 Chet Ramey <chet.ramey@case.edu> wrote:

> On 9/19/23 7:43 PM, Adam Thornton wrote:
>
> > Why (and when) did GNU drop the HISTORY section from its man pages?
>
> We never had it. It originated with 4.4 BSD, and none of us picked it up.
>

I recently added a HISTORY section to the Linux man-pages (chapters 2 and
3), and we moved there info that was scattered across various sections.  If
your plan includes man2 and man3, you could maybe just contribute some
extra details to those pages' HISTORY section and you're done with that
part.  We also produce a PDF book (this was done by Deri James from
gropdf): <https://mirrors.edge.kernel.org/pub/linux/docs/man-pages/book/>.

Cheers,


> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>
>

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

  reply	other threads:[~2023-09-20 14:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 20:32 [TUHS] " segaloco via TUHS
2023-09-19 23:39 ` [TUHS] " Larry McVoy
2023-09-20  1:26   ` segaloco via TUHS
2023-09-20  1:30     ` segaloco via TUHS
2023-09-20 14:57       ` Warner Losh
2023-09-20 15:40         ` Dan Cross
2023-09-20  2:09   ` Clem Cole
2023-09-20  2:25     ` Adam Thornton
2023-09-20  2:50       ` segaloco via TUHS
2023-09-20 19:56       ` Larry McVoy
2023-09-20 20:52         ` segaloco via TUHS
2023-09-20 22:31         ` Dave Horsfall
2023-09-21  4:09           ` Wesley Parish
2023-09-21 13:08             ` John P. Linderman
2023-09-21  0:26         ` Marc Donner
2023-09-21  3:06           ` Adam Thornton
2023-09-21  3:30             ` G. Branden Robinson
2023-09-21  3:48             ` Phil Budne
2023-09-21 13:37         ` Theodore Ts'o
2023-09-20 21:15       ` Alan Coopersmith
2023-09-21  3:49   ` G. Branden Robinson
2023-09-19 23:43 ` Adam Thornton
2023-09-20 13:23   ` Chet Ramey
2023-09-20 14:12     ` Alejandro Colomar (man-pages) [this message]
2023-09-19 23:47 ` KenUnix
2023-09-20  6:16 ` Jeremy C. Reed
2023-09-20  7:19   ` markus schnalke
2023-09-21 15:53 ` Kenneth Goodwin

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=CAJbEFzheZs-b4eS0OSi3s3kSc1jA3fhj+X5dOGNWQbT4+WXRQQ@mail.gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=segaloco@protonmail.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).