From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: release bugs [was Re: Processed: enriched.el code execution]
Date: Fri, 08 Sep 2017 23:42:30 +0200 [thread overview]
Message-ID: <87wp58yiih.fsf@qcore> (raw)
In-Reply-To: <CAFgFV9MPBaJNeBsSUbZBN2vbBE8nZmeKqiLtyzXm8+VvETJ4_g@mail.gmail.com> (Fabrice Popineau's message of "Fri, 8 Sep 2017 10:20:01 +0200")
Fabrice Popineau <fabrice.popineau@centralesupelec.fr> writes:
> Maybe I am naive, but I don't see why a bug existing in previous releases
> should be blocking.
We opened a secret door that can be used to cause harm to our users. It is
bad enough that we did that on past releases, but it would be totally
irresponsible to not fix our blunder on the next release.
> If the bug exists in say emacs 25.1, blocking the release of 26.1 will not
> prevent
> people to be at risk because they will continue to use 25.1.
This is why I'm with Paul about backporting the fix. This bug is truly
abhorrent.
[snip]
next prev parent reply other threads:[~2017-09-08 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83tw0h0yem.fsf@gnu.org>
[not found] ` <handler.s.C.150463767313430.transcript@debbugs.gnu.org>
2017-09-06 6:40 ` release bugs [was Re: Processed: enriched.el code execution] Glenn Morris
2017-09-06 9:41 ` John Wiegley
2017-09-06 10:00 ` Sven Joachim
2017-09-06 10:13 ` John Wiegley
2017-09-07 4:03 ` Richard Stallman
2017-09-07 14:43 ` Eli Zaretskii
2017-09-06 16:12 ` Eli Zaretskii
2017-09-07 6:30 ` Paul Eggert
2017-09-07 13:11 ` John Wiegley
2017-09-07 15:03 ` Eli Zaretskii
2017-09-07 21:32 ` Paul Eggert
2017-09-08 6:55 ` Eli Zaretskii
2017-09-08 7:11 ` Paul Eggert
2017-09-08 8:20 ` Fabrice Popineau
2017-09-08 21:42 ` Óscar Fuentes [this message]
2017-09-09 17:12 ` Richard Stallman
2017-09-09 18:27 ` Fabrice Popineau
2017-09-07 20:47 ` enriched.el code execution Reiner Steib
2017-09-07 21:24 ` Paul Eggert
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=87wp58yiih.fsf@qcore \
--to=ofv@wanadoo.es \
--cc=emacs-devel@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 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.