From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Simen Heggestøyl" <simenheg@runbox.com>,
"Philip K." <philipk@posteo.net>,
61976@debbugs.gnu.org, "Stefan Kangas" <stefankangas@gmail.com>,
"Noam Postavsky" <npostavs@gmail.com>
Subject: bug#61976: [elpa/yasnippet] [PATCH] Fix compilation warnings in Emacs 29
Date: Fri, 1 Sep 2023 22:16:26 +0100 [thread overview]
Message-ID: <CALDnm513xTroZb7Fhq6MzojvZ1b8O4K6L02kOv7cV0ngdPRXTQ@mail.gmail.com> (raw)
In-Reply-To: <jwvil8tk3f0.fsf-monnier+emacs@gnu.org>
On Fri, Sep 1, 2023 at 10:10 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> >> 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?
>
> Yes, please don't push to `elpa.git` directly (at least as long as the
> `:url` isn't nil in `elpa-packages`).
>
> > Could someone with access perhaps just push this patch to yasnippet on GitHub?
>
> I have more pending patches on `scratch/yasnippet` so you could push
> yours there, and then try and get someone at the upstream to pay
> attention to it?
> [ See https://github.com/joaotavora/yasnippet/issues/1167 ]
People, I have to say I don't pay much attention to yasnippet these days.
I'm not the maintainer anymore, but Noam has also been absent for quite some
time. I think it's time I archive the repository and it lives on in
elpa.git.
Then you can push this and all and other patches there.
WDYT?
João
next prev parent reply other threads:[~2023-09-01 21:16 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 ` bug#61976: [elpa/yasnippet] [PATCH] Fix compilation warnings in Emacs 29 Stefan Kangas
2023-09-01 21:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 21:16 ` João Távora [this message]
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=CALDnm513xTroZb7Fhq6MzojvZ1b8O4K6L02kOv7cV0ngdPRXTQ@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=61976@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=philipk@posteo.net \
--cc=simenheg@runbox.com \
--cc=stefankangas@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 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.