From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 65000@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#65000] [PATCH] gnu: emacs-next: Update to 29.1.
Date: Tue, 01 Aug 2023 23:10:26 +0200 [thread overview]
Message-ID: <71805be52c003be31f9cad04b18d4ab4@tobias.gr> (raw)
In-Reply-To: <a24d7d23acdcc6cd8a23c82416750ebf9b4cbeb1.camel@gmail.com>
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.
> Quite a number of prerequisites ;)
Local branches are for gits! Constantly rebasing keeps the fingers
strong.
Buff regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-08-01 22:39 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 [this message]
2023-08-02 4:25 ` Liliana Marie Prikler
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=71805be52c003be31f9cad04b18d4ab4@tobias.gr \
--to=guix-patches@gnu.org \
--cc=65000@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=liliana.prikler@gmail.com \
--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).