From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>,
p.stephani2@gmail.com, nilsb@google.com,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Making better use of the "release blocking list" [was: bug#23288: 25.0.92; Clicking on links inserts primary X selection]
Date: Mon, 16 May 2016 15:08:29 -0400 [thread overview]
Message-ID: <1v60ud253m.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <33d66ff1-7bf2-2ba5-29d9-b510bf1e344e@cs.ucla.edu> (Paul Eggert's message of "Thu, 12 May 2016 14:43:40 -0700")
"Blocking" is just the debbugs terminology. When I add something to
this list, it is something I think needs "attention" before the
release. (I tend to throw any obvious regression wrt to 24 on there.)
"Attention" can mean someone taking 30 seconds to make an informed
comment "this isn't an issue for 25.1 because X". (In which case they
may want to shift it to #21966.)
I'd hope it would go without saying, but feel free to remove things
If I disagree, I'll comment in the relevant report.
(BTW, I've never claimed my additions are exhaustive.)
next prev parent reply other threads:[~2016-05-16 19:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wvr4ziswfk37.fsf@a.muc.corp.google.com>
[not found] ` <CAGpFBBs-1CapH0nC3rFJG=QDygL_ASqQJbw+JMaKW_c5AQLoSA@mail.gmail.com>
[not found] ` <CAArVCkRAbt=F=-n-WdzZh5iQM3rXxWWCDhR3U3czgzLbugMfRQ@mail.gmail.com>
[not found] ` <CAGpFBBsk4WFWnxNFiiargUGiLjfcbSuugkL8iTv2BPsLQ-+sKQ@mail.gmail.com>
[not found] ` <CAArVCkTO26xRZPSa2+S58L2tjrrOi1bxUn+b+GCY9Tv2-WaQNw@mail.gmail.com>
[not found] ` <CAArVCkRXtiWh+T+=o9yNKjhG1QBdTCPbQWXmbch+t0Zc50bnPQ@mail.gmail.com>
[not found] ` <83mvnxau5t.fsf@gnu.org>
[not found] ` <CAArVCkR=EF1GMh1pnxiEsDs4KB4ry8+ZT71_3AR1szMz8+H6JQ@mail.gmail.com>
[not found] ` <83futobsw1.fsf@gnu.org>
[not found] ` <w94ma48mkp.fsf@fencepost.gnu.org>
[not found] ` <837ff0b931.fsf@gnu.org>
[not found] ` <mibn4bxlva.fsf@fencepost.gnu.org>
2016-05-12 17:21 ` Making better use of the "release blocking list" [was: bug#23288: 25.0.92; Clicking on links inserts primary X selection] John Wiegley
2016-05-12 21:43 ` Paul Eggert
2016-05-16 19:08 ` Glenn Morris [this message]
2016-05-18 6:09 ` John Wiegley
2016-05-21 19:06 ` Eli Zaretskii
2016-05-21 20:48 ` Mike Kupfer
2016-05-23 4:58 ` Bill Wohler
2016-05-30 23:21 ` Bill Wohler
2016-05-22 2:02 ` Paul Eggert
2016-05-22 4:52 ` John Wiegley
2016-05-22 16:38 ` Eli Zaretskii
2016-05-22 16:31 ` Eli Zaretskii
2016-05-22 21:09 ` Dmitry Gutov
2016-05-22 21:24 ` Dmitry Gutov
2016-05-23 2:32 ` Eli Zaretskii
2016-05-23 13:18 ` Dmitry Gutov
2016-05-23 16:15 ` Paul Eggert
2016-05-23 16:36 ` Dmitry Gutov
2016-05-23 17:39 ` Paul Eggert
2016-05-23 16:52 ` Eli Zaretskii
2016-05-13 9:02 ` Eli Zaretskii
2016-05-13 16:36 ` John Wiegley
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=1v60ud253m.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nilsb@google.com \
--cc=p.stephani2@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).