From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, John Wiegley <jwiegley@gmail.com>
Cc: 26952@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#26952: 25.1; loops eating all memory while yanking big rectangle
Date: Thu, 25 May 2017 09:19:50 -0700 [thread overview]
Message-ID: <4dacb636-0cae-9cb6-8491-2630e763d956@cs.ucla.edu> (raw)
In-Reply-To: <83lgplkm64.fsf@gnu.org>
On 05/25/2017 08:09 AM, Eli Zaretskii wrote:
> I don't believe we could have Emacs 26.1 out
> earlier than in six months' time, basically what we had with every
> other .1 release.
I think 26.1 is a better way to go here, even if we have to wait six
months for it. Users have already been living with this bug since 25.1's
release eight months ago, and they can wait a few months more.
We can publish 26.1 earlier if we don't run it through our leisurely six
month test period. It would not be tested as well as 25.1 was, but the
same would be true for any 25.3 release, as its changes are not likely
to be trivial to develop. We could warn users that 26.1 is more
experimental than 25.1 was, so that users not seriously affected by
Bug#26952 (i.e., most users) could stick with Emacs 25 if they want to
be conservative.
next prev parent reply other threads:[~2017-05-25 16:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 14:53 bug#26952: 25.1; loops eating all memory while yanking big rectangle Francesco Potortì
2017-05-20 0:24 ` npostavs
2017-05-20 9:59 ` Eli Zaretskii
2017-05-20 17:41 ` npostavs
2017-05-20 17:59 ` Eli Zaretskii
2017-05-20 19:27 ` npostavs
2017-05-21 15:28 ` Eli Zaretskii
2017-05-21 16:00 ` npostavs
2017-05-21 16:10 ` Eli Zaretskii
2017-05-21 16:48 ` npostavs
2017-05-21 19:15 ` Paul Eggert
2017-05-21 19:53 ` Eli Zaretskii
2017-05-21 20:20 ` Paul Eggert
2017-05-21 20:40 ` npostavs
2017-05-21 20:40 ` Paul Eggert
2017-05-21 20:52 ` npostavs
2017-05-22 4:01 ` Eli Zaretskii
2017-05-25 5:31 ` John Wiegley
2017-05-25 15:09 ` Eli Zaretskii
2017-05-25 16:19 ` Paul Eggert [this message]
2017-05-25 16:41 ` Francesco Potortì
2017-05-25 17:20 ` Eli Zaretskii
2017-05-27 1:15 ` Glenn Morris
2017-05-27 6:57 ` Paul Eggert
2017-05-27 7:42 ` Eli Zaretskii
2017-05-25 16:48 ` John Wiegley
2017-05-25 17:18 ` Noam Postavsky
2017-05-25 17:29 ` Francesco Potortì
2017-05-25 17:42 ` Noam Postavsky
2017-05-25 17:45 ` Eli Zaretskii
2017-05-25 19:24 ` Paul Eggert
2017-05-25 19:34 ` Eli Zaretskii
2017-05-25 20:59 ` Paul Eggert
2017-05-26 6:25 ` Eli Zaretskii
2017-05-26 15:24 ` Paul Eggert
2017-05-21 20:06 ` npostavs
2017-05-22 3:58 ` Eli Zaretskii
2020-01-08 16:45 ` bug#26952: Possible regression of Bug#26952 - "repeated buffer insertion consumes excessive memory" Peter Ludemann
2020-01-09 0:08 ` bug#39045: Fwd: Possible regression " Peter Ludemann
2022-05-23 10:48 ` Lars Ingebrigtsen
2022-06-21 11:46 ` Lars Ingebrigtsen
2020-01-09 0:10 ` bug#26952: Possible regression of Bug#26952 " Peter Ludemann
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=4dacb636-0cae-9cb6-8491-2630e763d956@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=26952@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jwiegley@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).