bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH] Solaris EOL update
Date: Sat, 17 Feb 2024 19:24:36 -0800	[thread overview]
Message-ID: <20240218032436.108336-1-eggert@cs.ucla.edu> (raw)

* doc/solaris-versions: Solaris 11.4 EOL update.  Also mention 11.3.
---
 ChangeLog            | 5 +++++
 doc/solaris-versions | 6 +++---
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 6c50c3574d..250db951e5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2024-02-17  Paul Eggert  <eggert@cs.ucla.edu>
+
+	Solaris EOL update
+	* doc/solaris-versions: Solaris 11.4 EOL update.  Also mention 11.3.
+
 2024-02-17  Collin Funk  <collin.funk1@gmail.com>
 
 	math: More clang -Winclude-next-absolute-path silencing.
diff --git a/doc/solaris-versions b/doc/solaris-versions
index f933518baa..ae064cea1c 100644
--- a/doc/solaris-versions
+++ b/doc/solaris-versions
@@ -47,9 +47,9 @@ After SunOS 5.6, they started numbering based on the second digit.
 The common terminology is to use the name "SunOS ..." to designate SunOS 2.x,
 3.x, 4.x, and "Solaris ..." or "Illumos" to designate SunOS 5.x.
 
-Most of these operating systems are obsolete.  As of 2023-07-11 only
-Solaris 10 (end-of-life January 2025) and Solaris 11 (end-of-life
-November 2034) are supported by Oracle and are therefore of
+Most of these operating systems are obsolete.  As of 2024-02-17 only
+Solaris 10 and 11.3 (both end-of-life January 2027) and Solaris 11.4
+(end-of-life November 2037) are supported by Oracle and are therefore of
 practical porting concern for GNU applications.  For the current list, see
 <https://en.wikipedia.org/wiki/Solaris_(operating_system)#Version_history>.
 
-- 
2.40.1



                 reply	other threads:[~2024-02-18  3:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240218032436.108336-1-eggert@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --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).