From: Stefan Kangas <stefankangas@gmail.com>
To: "Simen Heggestøyl" <simenheg@runbox.com>,
"João Távora" <joaotavora@gmail.com>
Cc: "Philip K." <philipk@posteo.net>,
61976@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#61976: [elpa/yasnippet] [PATCH] Fix compilation warnings in Emacs 29
Date: Fri, 1 Sep 2023 21:46:36 +0200 [thread overview]
Message-ID: <CADwFkmn4vrR2z8kD-zRP=37g4sR6R4C4wtVoSZCyKAqWAOrXfw@mail.gmail.com> (raw)
In-Reply-To: <6404531a.050a0220.40f60.a17aSMTPIN_ADDED_BROKEN@mx.google.com>
Simen Heggestøyl <simenheg@runbox.com> writes:
> Hi. The attached patch fixes the compilation warnings in yasnippet.el
> when compiling with Emacs 29.
Hmm. Yasnippet seems to be maintained on Github these days, and AFAIU
we pull from there automatically. Wouldn't installing it directly on
elpa.git lead to conflicts?
Could someone with access perhaps just push this patch to yasnippet on GitHub?
next parent reply other threads:[~2023-09-01 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6404531a.050a0220.40f60.a17aSMTPIN_ADDED_BROKEN@mx.google.com>
2023-09-01 19:46 ` Stefan Kangas [this message]
2023-09-01 21:10 ` bug#61976: [elpa/yasnippet] [PATCH] Fix compilation warnings in Emacs 29 Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 21:16 ` João Távora
2023-09-01 21:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 23:59 ` Stefan Kangas
2023-09-02 4:21 ` João Távora
2023-09-02 19:14 ` Stefan Kangas
2023-09-02 19:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 0:07 ` João Távora
2023-09-04 21:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 21:22 ` João Távora
2023-09-04 22:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-05 8:29 Simen Heggestøyl
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='CADwFkmn4vrR2z8kD-zRP=37g4sR6R4C4wtVoSZCyKAqWAOrXfw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=61976@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=philipk@posteo.net \
--cc=simenheg@runbox.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 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.