From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Wed, 27 Mar 2024 15:07:30 +0100 [thread overview]
Message-ID: <87zfujdazh.fsf@gmx.de> (raw)
In-Reply-To: <86frwbj171.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 27 Mar 2024 14:42:26 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
> So what is it that you do with Tramp to make its parts in Emacs ready
> for a release? If I'd alerted you to the imminent release, what would
> you have done before telling me that Tramp is ready?
I would change the Tramp version from "2.6.3-pre" to "2.6.3.29.3", and I
would update `customize-package-emacs-version-alist'.
The Tramp version happens on several places in Emacs, so I have a small
automation which runs on my laptop. See lisp/net/trampver.el and
doc/misc/trampver.texi.
>> I haven't proposed that such an announcement shall happen. I have only
>> proposed to send an alert like "Heads up! The next Emacs release will
>> happen on Sunday!".
>
> Without any explanation, that wouldn't be accepted by the community as
> we know it. There would be a flood of questions, and what could I
> possibly say in response? "I can tell you, but then I'll have to have
> you taken out and shot"?
If it doesn't bother you too much, an alert just to me would be OK.
>> Btw, I've got already the first rant that "Tramp 2.6.3-pre" is useless
>> for determining, whether a given patch is contained in Emacs 29.3. Right
>> they are!
>>
>> <https://github.com/magit/magit/issues/3624#issuecomment-2022167445>
>
> If you think this is bad enough, we can always release Emacs 29.4.
No. As I've said already in another message, this ship has sailed. And
it happened already in the past: Emacs 22.3 came with Tramp 2.0.58-pre,
and Emacs 23.4 came with Tramp 2.1.21-pre.
Best regards, Michael.
next prev parent reply other threads:[~2024-03-27 14:07 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfujdazh.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.