[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly
From: |
Eli Zaretskii |
Subject: |
bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled |
Date: |
Thu, 22 Feb 2018 09:39:37 +0200 |
> Cc: chris.w.feng@gmail.com, 23980@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 21 Feb 2018 23:45:30 +0200
>
> > I'm _really_ uneasy about putting this on the release branch. sit-for
> > is notorious for subtle problems that take a lot of time to be
> > exposed.
>
> Well, ok. I can live with that.
>
> Maybe consider it for inclusion if we end up having more pretests? This
> patch has been in master for a few months, and it's two lines long, so
> it must be *somewhat* safe.
Yes, a good idea.
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Dmitry Gutov, 2018/02/20
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Eli Zaretskii, 2018/02/20
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Dmitry Gutov, 2018/02/20
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Eli Zaretskii, 2018/02/20
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Chris Feng, 2018/02/21
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Dmitry Gutov, 2018/02/21
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Dmitry Gutov, 2018/02/21
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Eli Zaretskii, 2018/02/21
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled, Dmitry Gutov, 2018/02/21
- bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled,
Eli Zaretskii <=