From: Noam Postavsky <npostavs@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 24655@debbugs.gnu.org
Subject: bug#24655: Release 26.1
Date: Mon, 27 May 2019 21:21:58 -0400 [thread overview]
Message-ID: <87pno374qx.fsf@gmail.com> (raw)
In-Reply-To: <b8woudmtr9.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 02 Jul 2018 13:26:35 -0400")
# 28596: Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news,
# 25197: 26.0.50; notifications-notify is extremely slow with double buffering,
# 25474: 26.0.50; Buffer content invisible over remote display (SecureCRT + VcXsrv) when double buffering enabled,
# 28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux,
# 28652: 26.0.60; Display often "flashes" due to double buffering when switching to Emacs frames
unblock 24655 by 28596 25197 25474 28695 28652
close 24655
quit
Glenn Morris <rgm@gnu.org> writes:
> Presumably this report can be closed, but probably someone should first
> review the blocking bugs that were never fixed and decide whether they
> should be added to whatever mechanism is keeping the list for 27.1 / 26.2.
I'd say the remaining open blocking bugs should not block any release.
The double buffering graphical glitching/slowness is annoying for those
who hit it, but not that widespread as far as I can tell, and it can be
circumvented by turning off double buffering.
We're not seeing any movement or similar reports for the Gnus
plugged/unplugged thing.
prev parent reply other threads:[~2019-05-28 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83pon8ed50.fsf@gnu.org>
[not found] ` <handler.24655.Q.147609368731470.ackquiet@debbugs.gnu.org>
2018-07-02 17:26 ` bug#24655: Release 26.1 Glenn Morris
2019-05-28 1:21 ` Noam Postavsky [this message]
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=87pno374qx.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=24655@debbugs.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 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.