all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Sat, 06 Apr 2024 19:09:50 +0300	[thread overview]
Message-ID: <86y19q1nht.fsf@gnu.org> (raw)
In-Reply-To: <CAM=F=bC3Mbu2Mx-p7+xSp_GJhhsdU5Oc8bF3rR2mtpU9XWvEPQ@mail.gmail.com> (message from Lynn Winebarger on Sat, 6 Apr 2024 11:45:58 -0400)

> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Sat, 6 Apr 2024 11:45:58 -0400
> Cc: emacs-devel@gnu.org
> 
> On Sun, Mar 24, 2024 at 10:16 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > Version 29.3 of Emacs, the extensible text editor, should now
> > be available from your nearest GNU mirror:
> > [....]
> > Emacs 29.3 is an emergency bugfix release; it includes no new features
> > except a small number of changes intended to resolve security
> > vulnerabilities uncovered in Emacs 29.2.  See the file etc/NEWS in the
> > tarball; you can view it from Emacs by typing 'C-h n', or by clicking
> > Help->Emacs News from the menu bar.
> >
> Given the conservative nature of changes in minor releases, is it safe
> to assume the configure script options for a major release won't
> change in a minor release after X.1?

They shouldn't, not unless we discover some serious bug in those
options.

> You've been explicit here about no new features being added, but it
> would be nice to know in general if I can just use the same
> configure options from one minor release to the next without missing
> out on something new.

There are no changes in the configure script in Emacs 29.3.  You can
review all the changes by looking at the logs, whether Git logs or
ChangeLog.4 file in the top-level directory.



      reply	other threads:[~2024-04-06 16:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 14:14 Emacs 29.3 released Eli Zaretskii
2024-03-24 17:52 ` Corwin Brust
2024-03-24 18:46   ` Eli Zaretskii
2024-03-24 19:36     ` Corwin Brust
2024-03-24 19:46       ` Eli Zaretskii
2024-03-24 19:58         ` Eli Zaretskii
2024-03-27  5:54         ` Corwin Brust
2024-03-24 18:48 ` Michael Albinus
2024-03-24 19:29   ` Eli Zaretskii
2024-03-24 20:10     ` Michael Albinus
2024-03-24 20:20       ` Eli Zaretskii
2024-03-26  8:48         ` Michael Albinus
2024-03-26 12:46           ` Eli Zaretskii
2024-03-26 14:28             ` Michael Albinus
2024-03-26 14:38               ` Ihor Radchenko
2024-03-26 17:50                 ` Michael Albinus
2024-03-26 18:01                   ` Ihor Radchenko
2024-03-26 18:48                     ` Michael Albinus
2024-03-26 19:35               ` Eli Zaretskii
2024-03-27  8:27                 ` Michael Albinus
2024-03-27 12:42                   ` Eli Zaretskii
2024-03-27 14:07                     ` Michael Albinus
2024-03-27 16:42                       ` Eli Zaretskii
2024-03-27 17:35                         ` Michael Albinus
2024-04-03 12:03                           ` Michael Albinus
2024-04-03 12:36                             ` Robert Pluim
2024-04-03 15:01                               ` Michael Albinus
2024-04-03 12:51                             ` Eli Zaretskii
2024-04-03 14:56                               ` Michael Albinus
2024-04-04 12:25                                 ` Eli Zaretskii
2024-04-04 12:40                                   ` Michael Albinus
2024-04-04 17:46                                   ` Ihor Radchenko
2024-03-27 15:15                     ` Corwin Brust
2024-03-26 15:32   ` Ulrich Mueller
2024-03-26 18:42     ` Michael Albinus
2024-04-06 15:45 ` Lynn Winebarger
2024-04-06 16:09   ` Eli Zaretskii [this message]

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=86y19q1nht.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=owinebar@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.