From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: Philip Kaludercic <philipk@posteo.net>,
Stefan Kangas <stefankangas@gmail.com>,
60990-done@debbugs.gnu.org
Subject: bug#60990: 29.0.60; New seq release 2.24
Date: Mon, 04 Sep 2023 16:11:41 -0400 [thread overview]
Message-ID: <jwv1qfdpuo5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1886c406-0af0-a385-02f7-d7a89d247249@daniel-mendler.de> (Daniel Mendler's message of "Mon, 4 Sep 2023 21:23:09 +0200")
> Thanks! Btw, it seems that seq 2.24 is the last version which can be
> distributed via ELPA since Emacs 29 preloads seq.
Maybe it's OK to leave seq at 2.24 on ELPA. The main purpose of putting
it up on ELPA was to encourage adoption and accommodate changes more
easily, but it's now mature enough that changes are fairly slow, so we
can now rely on "the usual" solutions to deal with compatibility issues,
I think.
Stefan
next prev parent reply other threads:[~2023-09-04 20:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 14:51 bug#60990: 29.0.60; New seq release 2.24 Daniel Mendler
2023-09-04 15:32 ` Stefan Kangas
2023-09-04 16:16 ` Daniel Mendler
2023-09-04 17:05 ` Stefan Kangas
2023-09-04 17:32 ` Daniel Mendler
2023-09-04 18:35 ` Stefan Kangas
2023-09-04 19:23 ` Daniel Mendler
2023-09-04 20:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-04 20:35 ` Stefan Kangas
2023-09-04 21:12 ` Daniel Mendler
2023-09-04 22:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 7:44 ` Daniel Mendler
2023-09-09 8:15 ` Daniel Mendler
2023-09-09 12:28 ` Stefan Kangas
2023-09-09 13:42 ` Daniel Mendler
2023-09-09 21:57 ` Stefan Kangas
2023-09-09 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 16:07 ` Daniel Mendler
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=jwv1qfdpuo5.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=60990-done@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--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.