From: Andy Gaynor <goldipox@mail.com>
To: 54501@debbugs.gnu.org
Subject: bug#54501: 27.2; to be disclosed in private
Date: Mon, 21 Mar 2022 15:26:02 +0100 [thread overview]
Message-ID: <trinity-3fb98d93-dfba-4296-8aa2-25b533a96589-1647872762799@3c-app-mailcom-lxa14> (raw)
[-- Attachment #1: Type: text/html, Size: 6086 bytes --]
next reply other threads:[~2022-03-21 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:26 Andy Gaynor [this message]
2022-03-22 14:44 ` bug#54501: Segfault on recursive structure Lars Ingebrigtsen
2022-03-22 15:02 ` Andreas Schwab
2022-03-22 15:04 ` Lars Ingebrigtsen
[not found] ` <trinity-1bb5c502-bafe-4a6c-b6be-08a2a1b27232-1648049044877@3c-app-mailcom-lxa04>
2022-03-25 15:34 ` Lars Ingebrigtsen
2022-03-26 15:58 ` Mattias Engdegård
2022-03-26 16:33 ` Lars Ingebrigtsen
[not found] ` <8F7060F3-8137-4835-873F-68E3F6B8010D@acm.org>
2022-03-26 17:43 ` Mattias Engdegård
2022-03-26 18:00 ` 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
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=trinity-3fb98d93-dfba-4296-8aa2-25b533a96589-1647872762799@3c-app-mailcom-lxa14 \
--to=goldipox@mail.com \
--cc=54501@debbugs.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 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).