From: Michael Albinus <michael.albinus@gmx.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Tue, 26 Mar 2024 19:48:15 +0100 [thread overview]
Message-ID: <87o7b0esnk.fsf@gmx.de> (raw)
In-Reply-To: <87ttks98j7.fsf@localhost> (Ihor Radchenko's message of "Tue, 26 Mar 2024 18:01:48 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
Hi Ihor,
> Maybe you can split the versions into Emacs-only and, fuller, proper
> bugfix. Say, something like
> Tramp 2.6.2.<emacs>.<N> and Tramp 2.6.2.<elpa>.<N>
> Then, if emacs=1 and elpa=2, you will always get ELPA version to be
> newer compared to Emacs pretest version.
>
> But it is getting complicated... Not sure if it is worth layering the
> versions that much.
And don't forget, Tramp is almost a one-man-show.
>> I haven't seen any CVE number in the announcement.
>
> https://security-tracker.debian.org/tracker/CVE-2024-30203
>
> The Emacs release was the announcement, and the first public disclosure
> of the vulnerability.
So we would have had time alerting Emacs developers about the new
release in advance, wouldn't we?
Best regards, Michael.
next prev parent reply other threads:[~2024-03-26 18:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 14:14 Emacs 29.3 released Eli Zaretskii
2024-03-24 17:52 ` Corwin Brust
2024-03-24 18:46 ` Eli Zaretskii
2024-03-24 19:36 ` Corwin Brust
2024-03-24 19:46 ` Eli Zaretskii
2024-03-24 19:58 ` Eli Zaretskii
2024-03-27 5:54 ` Corwin Brust
2024-03-24 18:48 ` Michael Albinus
2024-03-24 19:29 ` Eli Zaretskii
2024-03-24 20:10 ` Michael Albinus
2024-03-24 20:20 ` Eli Zaretskii
2024-03-26 8:48 ` Michael Albinus
2024-03-26 12:46 ` Eli Zaretskii
2024-03-26 14:28 ` Michael Albinus
2024-03-26 14:38 ` Ihor Radchenko
2024-03-26 17:50 ` Michael Albinus
2024-03-26 18:01 ` Ihor Radchenko
2024-03-26 18:48 ` Michael Albinus [this message]
2024-03-26 19:35 ` Eli Zaretskii
2024-03-27 8:27 ` Michael Albinus
2024-03-27 12:42 ` Eli Zaretskii
2024-03-27 14:07 ` Michael Albinus
2024-03-27 16:42 ` Eli Zaretskii
2024-03-27 17:35 ` Michael Albinus
2024-04-03 12:03 ` Michael Albinus
2024-04-03 12:36 ` Robert Pluim
2024-04-03 15:01 ` Michael Albinus
2024-04-03 12:51 ` Eli Zaretskii
2024-04-03 14:56 ` Michael Albinus
2024-04-04 12:25 ` Eli Zaretskii
2024-04-04 12:40 ` Michael Albinus
2024-04-04 17:46 ` Ihor Radchenko
2024-03-27 15:15 ` Corwin Brust
2024-03-26 15:32 ` Ulrich Mueller
2024-03-26 18:42 ` Michael Albinus
2024-04-06 15:45 ` Lynn Winebarger
2024-04-06 16:09 ` Eli Zaretskii
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=87o7b0esnk.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/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).