From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: luangruo@yahoo.com, 56095@debbugs.gnu.org
Subject: bug#56095: 29.0.50; nsterm.m, use after free
Date: Wed, 22 Jun 2022 19:14:22 +0300 [thread overview]
Message-ID: <83tu8ciskh.fsf@gnu.org> (raw)
In-Reply-To: <8f6b9a15-a8c8-43c9-b903-7a1e1d023c61@Spark> (message from Gerd Möllmann on Wed, 22 Jun 2022 16:15:16 +0200)
> Date: Wed, 22 Jun 2022 16:15:16 +0200
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 56095-done@debbugs.gnu.org
>
> Btw, Gerd, I think you still have write access to the project's
> repository, so in principle you could install changes yourself.
> (If that doesn't work, let me know.)
>
> For now I'd rather submit patches. I'm so completely out of the loop for so long that I don't feel confident to
> do the right thing.
Fair enough.
next prev parent reply other threads:[~2022-06-22 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 14:28 bug#56095: 29.0.50; nsterm.m, use after free Gerd Möllmann
2022-06-20 1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 6:02 ` Gerd Möllmann
2022-06-20 10:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-21 14:25 ` Gerd Möllmann
2022-06-21 15:43 ` Eli Zaretskii
2022-06-22 5:26 ` Gerd Möllmann
2022-06-22 9:19 ` Gerd Möllmann
2022-06-22 13:21 ` Eli Zaretskii
2022-06-22 13:43 ` Gerd Möllmann
2022-06-22 1:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-22 13:53 ` Eli Zaretskii
2022-06-22 14:15 ` Gerd Möllmann
2022-06-22 16:14 ` Eli Zaretskii [this message]
[not found] <27290ad8-4f51-41e5-9317-46e4b3c5dd6c@Spark>
2022-06-19 17:32 ` bug#56095: Patch Gerd Möllmann
2022-06-19 22:51 ` bug#56095: 29.0.50; nsterm.m, use after free Lars Ingebrigtsen
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=83tu8ciskh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56095@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.com \
/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).