From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: Why wasn't the 25.3 release based on the then-head of the emacs-25 branch?
Date: Thu, 14 Sep 2017 20:24:18 -0700 [thread overview]
Message-ID: <a0a62007-cc4b-0a2f-dcc2-00f8447e5f9a@cs.ucla.edu> (raw)
In-Reply-To: <x0inglnhu1.fsf@fencepost.gnu.org>
Glenn Morris wrote:
> There were very few
> changes in the emacs-25 branch post 25.2, and I don't see why they were
> omitted.
Eli decided on a very thin 25.3 release, with just a patch for the
newly-discovered serious bug, along with minimal other changes such as
renumbering 25.2 to 25.3.
> In particular, it's disappointing that 94a6c96 isn't included. This
> (security) issue was reported to emacs-devel three years ago.
Although I also argued privately for releasing based on the emacs-25 branch
instead of just a thin release, Eli worried that the other changes in emacs-25
(including the change you mention) might have caused problems in 25.3's hasty
release. As I recall, the security issue that you mention is not as serious as
the one fixed in 25.3, since it occurs only in an unlikely installation nowadays
(no gnutls library or binaries available) whereas the 25.3 issue is an easy way
to break into anyone using Gnus to read email.
next prev parent reply other threads:[~2017-09-15 3:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 20:30 Why wasn't the 25.3 release based on the then-head of the emacs-25 branch? Glenn Morris
2017-09-15 3:24 ` Paul Eggert [this message]
2017-09-15 6:23 ` Eli Zaretskii
2017-09-15 21:26 ` Tim Cross
2017-09-16 7:10 ` Eli Zaretskii
2017-09-15 23:39 ` Glenn Morris
2017-09-16 7:09 ` Eli Zaretskii
2017-09-16 20:20 ` Paul Eggert
2017-09-17 2:35 ` Eli Zaretskii
2017-09-17 5:14 ` Paul Eggert
2017-09-17 14:21 ` Eli Zaretskii
2017-09-17 17:40 ` Paul Eggert
2017-09-17 18:59 ` Eli Zaretskii
2017-09-17 22:44 ` Paul Eggert
2017-09-18 15:05 ` Eli Zaretskii
2017-09-18 17:10 ` Paul Eggert
2017-09-18 17:48 ` 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=a0a62007-cc4b-0a2f-dcc2-00f8447e5f9a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.
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).