[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why no
From: |
Alan Mackenzie |
Subject: |
Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not? |
Date: |
Wed, 22 Jan 2020 20:05:49 +0000 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
Hello, Eli.
On Wed, Jan 22, 2020 at 05:27:46 +0200, Eli Zaretskii wrote:
> > Date: Tue, 21 Jan 2020 20:34:53 +0000
> > Cc: address@hidden
> > From: Alan Mackenzie <address@hidden>
> > Hello, Eli.
> > Ping?
> > Could we move forward with this, please?
> What holds this? I wasn't aware we had yet to discuss something or
> decide.
Ah, sorry. I thought we were still negotiating it.
I've committed the fix to the emacs-27 branch, and will now close bug
#38691.
--
Alan Mackenzie (Nuremberg, Germany).
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?, Eli Zaretskii, 2020/01/03
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?, Alan Mackenzie, 2020/01/04
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?, Eli Zaretskii, 2020/01/05
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?, Alan Mackenzie, 2020/01/05
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?, Alan Mackenzie, 2020/01/21
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?, Eli Zaretskii, 2020/01/21
- Re: /* FIXME: Call signal_after_change! */ in callproc.c. Well, why not?,
Alan Mackenzie <=