From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: stefankangas@gmail.com, rpluim@gmail.com, kfogel@red-bean.com,
emacs-devel@gnu.org
Subject: Re: Emacs 28.2 released
Date: Wed, 14 Sep 2022 20:33:21 +0300 [thread overview]
Message-ID: <83v8pp274u.fsf@gnu.org> (raw)
In-Reply-To: <87leql6gy0.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 14 Sep 2022 18:47:51 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
> kfogel@red-bean.com, emacs-devel@gnu.org
> Date: Wed, 14 Sep 2022 18:47:51 +0200
>
> Stefan Kangas <stefankangas@gmail.com> writes:
>
> > It was a bit more work than that, but I've now pushed a preliminary
> > version to emacs-28.
> >
> > See here for the result:
> >
> > https://www.gnu.org/software/emacs/news/NEWS.28.2.html
>
> Great; that looks really good.
I don't like the result at all, and like even less what is intended to
be its usage. So please don't install that.
next prev parent reply other threads:[~2022-09-14 17:33 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 10:13 Emacs 28.2 released Stefan Kangas
2022-09-12 11:28 ` Michael Albinus
2022-09-12 11:55 ` Michael Albinus
2022-09-12 11:59 ` Eli Zaretskii
2022-09-12 12:00 ` Eli Zaretskii
2022-09-12 12:03 ` Michael Albinus
2022-09-12 12:20 ` Lars Ingebrigtsen
2022-09-12 20:59 ` Karl Fogel
2022-09-13 1:36 ` Stefan Kangas
2022-09-13 2:30 ` Eli Zaretskii
2022-09-13 9:39 ` Stefan Kangas
2022-09-13 12:03 ` Eli Zaretskii
2022-09-13 12:46 ` Stefan Kangas
2022-09-13 13:03 ` Lars Ingebrigtsen
2022-09-13 13:43 ` Robert Pluim
2022-09-13 13:55 ` Lars Ingebrigtsen
2022-09-14 16:43 ` Stefan Kangas
2022-09-14 16:47 ` Lars Ingebrigtsen
2022-09-14 17:33 ` Eli Zaretskii [this message]
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:37 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-14 16:54 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:38 ` Eli Zaretskii
2022-09-14 16:57 ` Karl Fogel
2022-09-14 18:34 ` Bob Rogers
2022-09-16 14:56 ` Stefan Kangas
2022-09-13 15:29 ` Karl Fogel
2022-09-13 15:49 ` Eli Zaretskii
2022-09-13 15:52 ` Eli Zaretskii
2022-09-14 16:59 ` Karl Fogel
2022-09-14 17:04 ` Eli Zaretskii
2022-09-13 17:23 ` Windows Binaries for " Corwin Brust
2022-09-13 17:47 ` Eli Zaretskii
2022-09-13 18:01 ` Corwin Brust
2022-09-13 18:13 ` Eli Zaretskii
2022-09-13 19:30 ` Corwin Brust
2022-09-13 18:27 ` Óscar Fuentes
2022-09-14 2:56 ` Corwin Brust
2022-09-13 23:11 ` Corwin Brust
2022-09-14 2:36 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2022-09-14 17:06 Karl Fogel
2022-09-14 17:21 ` Eli Zaretskii
2022-09-14 18:49 ` Karl Fogel
2022-09-14 18:56 ` Eli Zaretskii
2022-09-14 19:15 ` Karl Fogel
2022-09-14 19:21 ` Eli Zaretskii
2022-09-14 19:53 ` Karl Fogel
2022-09-15 6:58 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-15 17:59 ` Karl Fogel
2022-09-14 17:39 ` Eli Zaretskii
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=83v8pp274u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
--cc=stefankangas@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).