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: 60990-done@debbugs.gnu.org
Subject: bug#60990: 29.0.60; New seq release 2.24
Date: Mon, 4 Sep 2023 18:16:54 +0200	[thread overview]
Message-ID: <ed445813-af20-55fb-1d62-4d247a2082bf@daniel-mendler.de> (raw)
In-Reply-To: <CADwFkm=aF_hBk8s-UAHq1mORwe2H0Z9Bjtd9ENSPN8xCPzCB+Q@mail.gmail.com>

Hello Stefan,

can we also get a new seq release 2.24 on ELPA? My report was about both
tagging a new seq version in Emacs and a new release on ELPA. Thanks!

Daniel

On 9/4/23 17:32, Stefan Kangas wrote:
> Version: 29.2
> 
> Daniel Mendler <mail@daniel-mendler.de> writes:
> 
>> The seq package has seen multiple additions since the seq 2.23 release.
>> Would it be possible to release a new version 2.24 and bump the version
>> in Emacs 29? With such a seq release 2.24, which coincides with Emacs 29,
>> packages depending 2.24 would not pull in the additional package if
>> installed on Emacs 29.
>>
>> In GNU Emacs 29.0.60 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo
>>  version 1.16.0, Xaw scroll bars) of 2023-01-14 built on projects
>> Repository revision: 8d7ad65665833ae99b7e7119dae37afa438968a4
>> Repository branch: emacs-29
>> Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
>> System Description: Debian GNU/Linux 11 (bullseye)
> 
> It seems we dropped the ball here and released Emacs 29.1 with seq.el
> versioned as 2.23.  I've now bumped the seq version to 2.24, so that we
> won't have the same problem in Emacs 29.2.
> 
> With that, I'm closing this bug report.





  reply	other threads:[~2023-09-04 16:16 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 [this message]
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
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=ed445813-af20-55fb-1d62-4d247a2082bf@daniel-mendler.de \
    --to=mail@daniel-mendler.de \
    --cc=60990-done@debbugs.gnu.org \
    --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).