From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Michael Albinus <michael.albinus@gmx.de>
Cc: stefan@marxist.se, 39200@debbugs.gnu.org
Subject: bug#39200: Release 27.1
Date: Mon, 24 Aug 2020 01:58:21 +0300 [thread overview]
Message-ID: <b9890fc4-fb86-b1e6-79cb-96990a72164a@yandex.ru> (raw)
In-Reply-To: <83pn7h6vbc.fsf@gnu.org>
On 23.08.2020 22:01, Eli Zaretskii wrote:
>>> We didn't miss them. I decided they weren't important enough to hold
>>> the release.
>> That's pretty OK as maintainer decision. But shouldn't the two bugs then
>> be removed from blocking ones for bug#39200? At least a communication
>> about this decision I have missed, perhaps because I didn't see it.
> Some people react emotionally when I close bugs against their
> opinions, so I sometimes decide not to do that.
I believe the suggestion was to remove them from blockers, not closing
them. If anyone objects to that, they would object to making a release
before the bugs as fixed as well.
next prev parent reply other threads:[~2020-08-23 22:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tv4qxr2x.fsf@gmx.de>
[not found] ` <handler.39200.Q.157952248126501.ackquiet@debbugs.gnu.org>
2020-08-23 13:26 ` bug#39200: Release 27.1 Stefan Kangas
2020-08-23 17:16 ` Michael Albinus
2020-08-23 18:44 ` Eli Zaretskii
2020-08-23 18:57 ` Michael Albinus
2020-08-23 19:01 ` Eli Zaretskii
2020-08-23 19:10 ` Michael Albinus
2020-08-23 19:13 ` Eli Zaretskii
2020-08-23 19:23 ` Michael Albinus
2020-08-23 19:43 ` Eli Zaretskii
2020-08-24 16:05 ` Michael Albinus
2020-08-24 16:11 ` Eli Zaretskii
2020-08-24 16:15 ` Michael Albinus
2020-08-23 22:58 ` Dmitry Gutov [this message]
2020-08-24 4:58 ` Eli Zaretskii
2020-08-23 19:06 ` Stefan Kangas
2020-08-23 19:17 ` Michael Albinus
2020-08-23 19:56 ` Stefan Kangas
2020-08-23 23:06 ` Noam Postavsky
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=b9890fc4-fb86-b1e6-79cb-96990a72164a@yandex.ru \
--to=dgutov@yandex.ru \
--cc=39200@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=stefan@marxist.se \
/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).