unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Mendler <mail@daniel-mendler.de>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
	60990-done@debbugs.gnu.org,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#60990: 29.0.60; New seq release 2.24
Date: Mon, 4 Sep 2023 21:23:09 +0200	[thread overview]
Message-ID: <1886c406-0af0-a385-02f7-d7a89d247249@daniel-mendler.de> (raw)
In-Reply-To: <CADwFkmkJWpeS+g3+m-3QQ14DWvotW=p7j+PVBAc3+Yk9g7xrxw@mail.gmail.com>

On 9/4/23 20:35, Stefan Kangas wrote:
> Daniel Mendler <mail@daniel-mendler.de> writes:
> 
>> How is that? I thought that seq is not a :core package, since it
>> supports Emacs versions from before the introduction of cl-defgeneric.
>> It has different code which must be updated manually and as such doesn't
>> automatically get released.
> 
> Uhm, yes, you're right of course.
> 
> I have now merged all the changes from master/emacs-29 (the branches are
> identical), and pushed it to elpa.git.

Thanks! Btw, it seems that seq 2.24 is the last version which can be
distributed via ELPA since Emacs 29 preloads seq. If Emacs 30 comes with
a hypothetical new seq 2.30 with new functions, a package requiring seq
2.30 cannot load seq on Emacs 29, since the feature is already loaded.
We could possibly work around this problem by distributing seq functions
from than 2.30 and newer via Compat. We should then document that
packages needing a seq newer than 2.24 should rely on Compat instead. I
am not sure if this is a desired solution though since it might be a bit
confusing. I've added Philip and Stefan M. in cc. What do you think?

Daniel





  reply	other threads:[~2023-09-04 19:23 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 [this message]
2023-09-04 20:11             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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

  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=1886c406-0af0-a385-02f7-d7a89d247249@daniel-mendler.de \
    --to=mail@daniel-mendler.de \
    --cc=60990-done@debbugs.gnu.org \
    --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 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).