From: Bob Kline <bkline@rksystems.com>
To: Po Lu <luangruo@yahoo.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Robert Pluim" <rpluim@gmail.com>,
57563@debbugs.gnu.org
Subject: bug#57563: 28.1; macOS - layout warning at startup
Date: Fri, 16 Sep 2022 10:33:14 -0400 [thread overview]
Message-ID: <CAGjKmVr1_3FoFPtu1wtrq8mf09ZrnvJQoLKn7vPw3Lnkrk2gzA@mail.gmail.com> (raw)
In-Reply-To: <CAGjKmVqt8-KkjND+9FB8bugyJwGkB6g-2m1n5WRu=MyUn8fc4g@mail.gmail.com>
On Fri, Sep 16, 2022 at 9:41 AM Bob Kline <bkline@rksystems.com> wrote:
> ...
> The current version of macOS is 12.6 (macOS Monterey), released last
> Fall, whereas macOS 10.12 is macOS Sierra, released in September 2016.
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53481#5
Oops, sorry, I had the wrong URL in my clipboard and didn't notice. It
should have been:
https://support.apple.com/en-us/HT201260
Basically, "OS X" and "macOS" do not represent different version
numbering series. They're just different prefix names applied by Apple
to the one version numbering series used over the past couple of
decades or so. See the "Is there any difference between Mac OS X and
macOS?" paragraph near the top of
https://setapp.com/how-to/full-list-of-all-macos-versions.
Apologies for the confusion. (And I'm sure Apple offers the same apology.) 😉
next prev parent reply other threads:[~2022-09-16 14:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 14:39 bug#57563: 28.1; macOS - layout warning at startup Bob Kline
2022-09-05 1:36 ` Lars Ingebrigtsen
2022-09-05 12:13 ` Bob Kline
2022-09-05 19:01 ` Lars Ingebrigtsen
2022-09-06 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-06 13:45 ` Bob Kline
2022-09-07 1:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-07 5:04 ` Gerd Möllmann
2022-09-07 12:17 ` Bob Kline
2022-09-07 12:28 ` Gerd Möllmann
2022-09-07 12:47 ` Bob Kline
2022-09-07 12:56 ` Gerd Möllmann
2022-09-07 12:59 ` Bob Kline
2022-09-07 13:03 ` Robert Pluim
2022-09-07 13:10 ` Bob Kline
2022-09-07 13:19 ` Robert Pluim
2022-09-07 13:22 ` Bob Kline
2022-09-07 13:45 ` Gerd Möllmann
2022-09-07 13:47 ` Gerd Möllmann
2022-09-07 13:41 ` Gerd Möllmann
2022-09-07 13:48 ` Bob Kline
2022-09-07 13:58 ` Gerd Möllmann
2022-09-07 14:18 ` Bob Kline
2022-09-07 18:01 ` Bob Kline
2022-09-08 5:02 ` Gerd Möllmann
2022-09-08 8:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 13:04 ` Bob Kline
2022-09-08 13:19 ` Gerd Möllmann
2022-09-08 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 13:55 ` Robert Pluim
2022-09-08 14:02 ` Bob Kline
2022-09-08 16:12 ` Bob Kline
2022-09-08 20:00 ` Bob Kline
2022-09-09 5:02 ` Gerd Möllmann
2022-09-09 8:55 ` Robert Pluim
2022-09-11 11:13 ` Bob Kline
2022-09-12 5:58 ` Gerd Möllmann
2022-09-12 11:11 ` Bob Kline
2022-09-12 11:35 ` Gerd Möllmann
2022-09-15 13:33 ` Bob Kline
2022-09-16 5:56 ` Gerd Möllmann
2022-09-16 13:16 ` Bob Kline
2022-09-16 13:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-16 13:41 ` Bob Kline
2022-09-16 14:33 ` Bob Kline [this message]
2022-09-17 1:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGjKmVr1_3FoFPtu1wtrq8mf09ZrnvJQoLKn7vPw3Lnkrk2gzA@mail.gmail.com \
--to=bkline@rksystems.com \
--cc=57563@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.com \
--cc=rpluim@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).