From: John Wiegley <jwiegley@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: 2 release blocking bugs left for 25.1!
Date: Tue, 21 Jun 2016 11:43:49 -0700 [thread overview]
Message-ID: <m260t2gz6i.fsf@newartisans.com> (raw)
In-Reply-To: <jwveg7q9249.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 21 Jun 2016 08:07:54 -0400")
>>>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> I'd like to suggest 23785 as a blocker also -- the bug (in the report) is
>>>> not too serious, but as a fix may involve a change in the command loop,
>>>> I'd rather do this before a RC.
>>> If the bug is not too serious, can you explain the rationale for making it
>>> a blocker?
>> The symptoms are not too serious, but it's a bug in the undo system, so may
>> have significant implications elsewhere.
> And it's a regression in 25.1 due to the new undo code.
This does sounds like a blocker, then. What are the repercussions for fixing
the issue? Will it need a full round of pretesting to become ready for the
release candidate?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-06-21 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 16:54 2 release blocking bugs left for 25.1! John Wiegley
2016-06-18 17:22 ` Eli Zaretskii
2016-06-18 17:24 ` John Wiegley
2016-06-18 17:38 ` Eli Zaretskii
2016-06-20 9:25 ` Nicolas Petton
2016-06-20 12:21 ` Phillip Lord
2016-06-20 23:26 ` John Wiegley
2016-06-21 11:40 ` Phillip Lord
2016-06-21 12:07 ` Stefan Monnier
2016-06-21 18:43 ` John Wiegley [this message]
2016-06-21 18:51 ` Eli Zaretskii
2016-06-21 20:14 ` John Wiegley
2016-06-21 20:43 ` Phillip Lord
2016-06-21 21:55 ` Óscar Fuentes
2016-06-22 17:25 ` Phillip Lord
2016-06-22 2:14 ` Paul Eggert
2016-06-28 2:56 ` Mark Oteiza
2016-06-28 16:30 ` Eli Zaretskii
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=m260t2gz6i.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).