From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: William C Doughty III <n2ocm@optonline.net>, 60884-done@debbugs.gnu.org
Subject: bug#60884: 30.0.50; Compile failure - followup
Date: Tue, 5 Sep 2023 17:07:32 -0700 [thread overview]
Message-ID: <CADwFkmkMobN-L-6L+Oy_wr5sfChg-0oM3rjDE5LuWUhYVJO2tw@mail.gmail.com> (raw)
In-Reply-To: <83h6wp2gx1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Jan 2023 19:46:02 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> This should be fixed now on the master branch.
No further comments within 9 months, so I'm assuming the fix worked.
I'm therefore closing this bug report.
prev parent reply other threads:[~2023-09-06 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 15:52 bug#60884: 30.0.50; Compile failure - followup William C Doughty III
2023-01-17 17:46 ` Eli Zaretskii
2023-09-06 0:07 ` Stefan Kangas [this message]
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=CADwFkmkMobN-L-6L+Oy_wr5sfChg-0oM3rjDE5LuWUhYVJO2tw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=60884-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=n2ocm@optonline.net \
/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).