From: Andrew Clayton <andrew@digital-domain.net>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Alejandro Colomar <alx@kernel.org>,
Andrew Clayton <andrew@digital-domain.net>
Subject: Re: [PATCH] memmem.3: Added list of known systems where this is available
Date: Thu, 10 Nov 2022 12:58:11 +0000 [thread overview]
Message-ID: <20221110125811.4d786437@kappa.digital-domain.net> (raw)
In-Reply-To: <853fa349-8e78-8ce8-f76f-79b4b9353913@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Thu, 10 Nov 2022 12:36:47 +0100
Alejandro Colomar <alx.manpages@gmail.com> wrote:
> Although for the page itself I wouldn't add the dates, I think it's useful to
> include the years of those releases in the commit message (when known).
>
> musl 0.9.7 is from 2012.
> FreeBSD 6 is from 2005.
> OpenBSD 5.4 is from 2013.
>
> Please include that, if you don't mind.
Will do.
[...]
> For the commit message, it's interesting to note macOS and Bionic, for
> speleology purposes. However, I'm opposed to adding them to the page itself
> because of the following:
>
> - macOS is not free software. I refuse to reference nonfree software on this
> project.
In that case you might want to remove references to the following (as
it looked OK to reference proprietary UNIX)
SunOS, Solaris, Irix, AIX, DG/UX, HP-UX, OSF/1, Digital UNIX, Tru64,
SCO (definitely SCO!), and MacOS X (and probably others I missed).
Personally I wouldn't, they're a part of Linux's history... and these
days largely interesting for historical purposes.
Cheers,
Andrew
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-10 12:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 0:13 [PATCH] memmem.3: Added list of known systems where this is available Andrew Clayton
2022-11-10 11:36 ` Alejandro Colomar
2022-11-10 12:58 ` Andrew Clayton [this message]
2022-11-10 14:16 ` Alejandro Colomar
2022-11-22 23:11 ` Guillem Jover
2022-11-23 12:52 ` Stefan Puiu
2022-11-23 13:16 ` Alejandro Colomar
2022-11-23 14:55 ` [musl] " Jeffrey Walton
2022-11-23 15:11 ` Alejandro Colomar
2022-11-24 18:57 ` Stefan Puiu
2022-12-11 16:30 ` Alejandro Colomar
2022-11-10 23:31 ` [PATCH v2] memmem.3: Add " Andrew Clayton
2022-11-10 23:59 ` Alejandro Colomar
2022-11-11 0:04 ` Andrew Clayton
2022-11-11 0:05 ` Alejandro Colomar
2022-11-11 0:20 ` Andrew Clayton
2022-11-11 0:21 ` Alejandro Colomar
2022-11-11 1:27 ` [PATCH v3] " Andrew Clayton
2022-11-11 1:35 ` Alejandro Colomar
2022-11-11 18:09 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2022-11-24 19:13 [PATCH] memmem.3: Added " Brian Inglis
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=20221110125811.4d786437@kappa.digital-domain.net \
--to=andrew@digital-domain.net \
--cc=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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