From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44313@debbugs.gnu.org, Aaron Jensen <aaronjensen@gmail.com>
Subject: bug#44313: 27.1.50; ns_mouse_position EXC_BAD_ACCESS crash
Date: Mon, 9 Nov 2020 14:54:50 +0000 [thread overview]
Message-ID: <20201109145450.GS59267@breton.holly.idiocy.org> (raw)
In-Reply-To: <87v9eelhfu.fsf@gnus.org>
On Mon, Nov 09, 2020 at 03:43:01PM +0100, Lars Ingebrigtsen wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > On Fri, Nov 06, 2020 at 08:29:34AM -0600, Aaron Jensen wrote:
> >> I've got even more time with this patch now and still no crashes. No
> >> other problems that I've seen either. It seems like a good change.
> >> Thanks, Alan. Would this be good to go in 27?
> >
> > I think so, unless anyone has any objections?
> >
> > It fixes a real world crash and is a very small change.
>
> My impression is that more people use the Emacs 28 branch than the 27
> branch, so for low-level changes like this, I think it's often
> preferable to apply them to Emacs 28 and then cherry-pick them for Emacs
> 27 after a week or so (if no problems have been seen).
I've pushed to master as 18a7267c32a909bb26bd93d24543155aeb10e042.
--
Alan Third
next prev parent reply other threads:[~2020-11-09 14:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 20:16 bug#44313: 27.1.50; ns_mouse_position EXC_BAD_ACCESS crash Aaron Jensen
2020-10-30 7:15 ` Eli Zaretskii
2020-10-30 10:16 ` Aaron Jensen
2020-10-30 11:29 ` Eli Zaretskii
2020-10-30 15:54 ` Aaron Jensen
2020-10-30 18:47 ` Eli Zaretskii
2020-10-30 18:55 ` Aaron Jensen
2020-10-30 19:07 ` Eli Zaretskii
2020-10-30 19:37 ` Aaron Jensen
2020-10-30 20:12 ` Eli Zaretskii
2020-10-30 20:18 ` Aaron Jensen
2020-10-30 22:35 ` Alan Third
2020-11-02 18:11 ` Aaron Jensen
2020-11-06 14:29 ` Aaron Jensen
2020-11-07 16:29 ` Alan Third
2020-11-09 14:43 ` Lars Ingebrigtsen
2020-11-09 14:54 ` Alan Third [this message]
2020-12-12 10:43 ` Alan Third
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=20201109145450.GS59267@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=44313@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=larsi@gnus.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 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).