From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 65000@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#65000] [PATCH] gnu: emacs-next: Update to 29.1.
Date: Wed, 02 Aug 2023 06:25:04 +0200 [thread overview]
Message-ID: <ea69d1d340a69b775fbdcf41ea40257b9981140e.camel@gmail.com> (raw)
In-Reply-To: <71805be52c003be31f9cad04b18d4ab4@tobias.gr>
Am Dienstag, dem 01.08.2023 um 23:10 +0200 schrieb Tobias Geerinckx-
Rice:
> On 2023-08-01 22:27, Liliana Marie Prikler wrote:
> > Welp, given that this is a release, it's no longer, "emacs-next",
> > isn't it?
>
> Oh? To me, "-next" does not imply ‘not a release’.
>
> It can mean all sorts of fun things, like ‘known to be broken if you
> hold it wrong’, ‘simply not as tested as the primary package’, or
> even ‘I didn't wanna wait for a whole proper "emacs" integration
> cycle to get this upstream ;-)’.
>
> Yeah, that's the one.
I mean, I can understand that. On the other hand, I don't think it'd
be nice for emacs-team to diverge too far and a merge in celebration of
"emacs-next" being actually released now would make a lot of sense
imho. That being said it would also mean that folks would have to
s/emacs-next/emacs their profiles.
Andrew, WDYT?
next prev parent reply other threads:[~2023-08-02 4:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 0:00 [bug#65000] [PATCH] gnu: emacs-next: Update to 29.1 Tobias Geerinckx-Rice via Guix-patches via
2023-08-01 20:27 ` Liliana Marie Prikler
2023-08-01 21:10 ` Tobias Geerinckx-Rice via Guix-patches via
2023-08-02 4:25 ` Liliana Marie Prikler [this message]
2023-08-02 10:20 ` Andrew Tropin
2023-08-14 5:45 ` Liliana Marie Prikler
2023-08-14 10:12 ` Andrew Tropin
2023-08-14 15:04 ` Liliana Marie Prikler
2023-08-14 15:31 ` Liliana Marie Prikler
2023-08-14 17:49 ` Andrew Tropin
2023-08-02 18:30 ` [bug#65000] [PATCH emacs-team v2] gnu: emacs: " Liliana Marie Prikler
2023-08-23 10:06 ` [bug#65000] [PATCH] gnu: emacs-next: " Ludovic Courtès
2023-08-23 12:13 ` Andrew Tropin
2023-08-23 16:54 ` bug#65000: " Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea69d1d340a69b775fbdcf41ea40257b9981140e.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=65000@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=me@tobias.gr \
/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/guix.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).