From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48029@debbugs.gnu.org, jakanakaevangeli@chiru.no, akrl@sdf.org
Subject: bug#48029: 28.1; [native-comp] Function names with non-ascii characters
Date: Sun, 10 Jul 2022 16:02:34 +0300 [thread overview]
Message-ID: <83fsj915p1.fsf@gnu.org> (raw)
In-Reply-To: <87o7xx3z3r.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 10 Jul 2022 14:56:40 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Andrea Corallo <akrl@sdf.org>, 48029@debbugs.gnu.org,
> jakanakaevangeli@chiru.no
> Date: Sun, 10 Jul 2022 14:56:40 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > To the release branch, if Lars agrees. But let's first try to see if
> > bug#45433 is not back after the above change.
>
> If it doesn't regress bug#45433, then it's fine by me.
Andrea says he cannot reproduce bug#45433 even if he removes the fix
entirely. I guess some other change fixed it.
next prev parent reply other threads:[~2022-07-10 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 8:53 bug#48029: 28.1; [native-comp] Function names with non-ascii characters jakanakaevangeli
2021-05-02 8:47 ` Lars Ingebrigtsen
2021-05-02 21:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-30 13:10 ` Lars Ingebrigtsen
2022-07-04 8:51 ` Andrea Corallo
2022-07-04 11:20 ` Eli Zaretskii
2022-07-07 8:58 ` Andrea Corallo
2022-07-07 17:47 ` Lars Ingebrigtsen
2022-07-07 20:51 ` Andrea Corallo
2022-07-08 5:43 ` Eli Zaretskii
2022-07-08 8:49 ` Andrea Corallo
2022-07-08 12:40 ` Eli Zaretskii
2022-07-08 13:43 ` Andrea Corallo
2022-07-08 13:59 ` Eli Zaretskii
2022-07-08 14:53 ` Andrea Corallo
2022-07-10 12:56 ` Lars Ingebrigtsen
2022-07-10 13:02 ` Eli Zaretskii [this message]
2022-07-12 14:24 ` Andrea Corallo
2022-07-12 15:40 ` Eli Zaretskii
2022-07-12 15:46 ` Lars Ingebrigtsen
2022-07-13 13:20 ` Andrea Corallo
2023-06-05 8:50 ` Andrea Corallo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fsj915p1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48029@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=jakanakaevangeli@chiru.no \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.