From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
mark.t.kennedy@gmail.com, 52833-done@debbugs.gnu.org
Subject: bug#52833: native compilation fails on teco.el from MELPA
Date: Mon, 17 Jan 2022 10:59:29 +0000 [thread overview]
Message-ID: <xjfczkq4oha.fsf@ma.sdf.org> (raw)
In-Reply-To: <831r19181i.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Jan 2022 14:46:01 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: mark.t.kennedy@gmail.com, 52833@debbugs.gnu.org, akrl@sdf.org
>> Date: Sat, 15 Jan 2022 13:31:31 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> > I've installed a fix on master as e7699bf290, please have a look if it
>> >> > works for you as well.
>> >> >
>> >> > Maintainers will tell us if we want to backport it on emacs-28 as well
>> >> > (I think would be worth).
>> >>
>> >> If it doesn't lead to any regressions on master, backporting it to
>> >> emacs-28 sounds like a good idea to me.
>> >
>> > Agreed, let's revisit this in a week or two.
>>
>> It's now been two weeks, so should this be backported now?
>
> I won't object to backporting it.
>
>> (I can't recall seeing any regressions, but I haven't paid that much
>> attention the past few weeks.)
>
> Neither did I.
Hi all,
I then pushed the backport into emacs-28 as 9e64aeff40.
Closing this.
Thanks!
Andrea
prev parent reply other threads:[~2022-01-17 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 20:40 bug#52833: native compilation fails on teco.el from MELPA Mark Kennedy
2021-12-28 15:05 ` Andrea Corallo
2021-12-28 15:09 ` Lars Ingebrigtsen
2021-12-28 15:21 ` Eli Zaretskii
2021-12-28 19:08 ` Mark Kennedy
2021-12-28 21:37 ` Andrea Corallo
2022-01-15 12:31 ` Lars Ingebrigtsen
2022-01-15 12:46 ` Eli Zaretskii
2022-01-17 10:59 ` Andrea Corallo [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=xjfczkq4oha.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=52833-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=mark.t.kennedy@gmail.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).