From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: dropping some old platforms from the doc
Date: Sat, 06 Jul 2019 02:27:45 +0200 [thread overview]
Message-ID: <5358627.jyL4EcGJXE@omega> (raw)
Hi,
I'd like to remove the mentions of the following old platforms from
the gnulib documentation:
Platform Comments
-------- --------
glibc < 2.2
Linux libc5
Mac OS X < 10.5
AIX < 5 end of support in 2004 (AIX 4.3.3 released in 1999)
HP-UX < 11 end of support in 2003 (HP-UX 10.30 released in 1997)
IRIX < 6.5 IRIX 6.5 released in 1998.
OSF/1 end of support in 2012 (OSF/1 5.1 released in 2000)
Solaris < 9 end of support in 2012 (Solaris 8 released in 2000)
Interix last supported in Windows 8 (Interix 6.1 released in 2010)
BeOS BeOS 5.1 released in 2001
The reason is that it starts to clutter up the documentation, when you're
looking for any more portability targets. Also, no one is testing these
platforms any more.
The corresponding code can still stay in gnulib, I don't mind. I'm
not religious about shorter or longer 'configure' execution times,
nor about the size of tarballs.
Bruno
next reply other threads:[~2019-07-06 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 0:27 Bruno Haible [this message]
2019-07-06 1:54 ` dropping some old platforms from the doc Paul Eggert
2019-07-06 14:57 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5358627.jyL4EcGJXE@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).