From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: release bugs [was Re: Processed: enriched.el code execution]
Date: Wed, 06 Sep 2017 19:12:43 +0300 [thread overview]
Message-ID: <83lglr24ck.fsf@gnu.org> (raw)
In-Reply-To: <bn1snkib3u.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 06 Sep 2017 02:40:05 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 06 Sep 2017 02:40:05 -0400
>
>
> I'm surprised that you don't want to motivate people to fix security
> vulnerabilities for the next release.
I do, I just don't see how can I justify delaying a release due to an
issue that was with us since 1999.
> Anyway, I'll stop adding to list of release bugs, since it feels unproductive.
It isn't unproductive, and I appreciate it very much that you are
doing it. I just wish you'd do it publicly, at least in controversial
cases such as this one.
Or maybe we could discuss the criteria for blocking bugs, and if
agreed, no further discussions would be necessary.
next prev parent reply other threads:[~2017-09-06 16:12 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 [this message]
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
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
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=83lglr24ck.fsf@gnu.org \
--to=eliz@gnu.org \
--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).