all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: emacs-devel@gnu.org
Cc: Nicolas Petton <nicolas@petton.fr>, Eli Zaretskii <eliz@gnu.org>,
	Richard Stallman <rms@gnu.org>
Subject: Re: 2 release blocking bugs left for 25.1!
Date: Tue, 21 Jun 2016 12:40:02 +0100	[thread overview]
Message-ID: <87fus6vkh9.fsf@russet.org.uk> (raw)
In-Reply-To: <m2fus7cui9.fsf@newartisans.com> (John Wiegley's message of "Mon,  20 Jun 2016 16:26:06 -0700")

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> Phillip Lord <phillip.lord@russet.org.uk> 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.

Phil



  reply	other threads:[~2016-06-21 11:40 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 [this message]
2016-06-21 12:07       ` Stefan Monnier
2016-06-21 18:43         ` John Wiegley
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fus6vkh9.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nicolas@petton.fr \
    --cc=rms@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.