From: Stefan Kangas <stefan@marxist.se>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 39200@debbugs.gnu.org
Subject: bug#39200: Release 27.1
Date: Sun, 23 Aug 2020 09:26:12 -0400 [thread overview]
Message-ID: <CADwFkmkk_JGoZGruSxY=8JVDOuX6LodnUMpsoE68a3kirAxMMg@mail.gmail.com> (raw)
In-Reply-To: <handler.39200.Q.157952248126501.ackquiet@debbugs.gnu.org> (GNU bug Tracking System's message of "Mon, 20 Jan 2020 12:15:01 +0000")
help-debbugs@gnu.org (GNU bug Tracking System) writes:
> Thank you for filing a new bug report with debbugs.gnu.org.
Seems like there are two blocking bugs here that were marked as blocking
release 27.1:
41423: 27.0.91; eshell file completion in tramp dir is slow (3 minutes)
[regression on pretest]
36006: electric-pair-mode fails to balance in certain cases
It doesn't seem ideal that we missed these outstanding and presumably
release critical bugs. Maybe someone should clean this up, and think
about how we should use bugs like this in the future.
Best regards,
Stefan Kangas
next parent reply other threads:[~2020-08-23 13:26 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 ` Stefan Kangas [this message]
2020-08-23 17:16 ` bug#39200: Release 27.1 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmkk_JGoZGruSxY=8JVDOuX6LodnUMpsoE68a3kirAxMMg@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=39200@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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.