From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 65000@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>,
Andrew Tropin <andrew@trop.in>
Subject: [bug#65000] [PATCH] gnu: emacs-next: Update to 29.1.
Date: Wed, 23 Aug 2023 12:06:45 +0200 [thread overview]
Message-ID: <87o7iy139m.fsf_-_@gnu.org> (raw)
In-Reply-To: <3349a50d700a2112a31ac4ce6cc6639d3b4cf1e2.1691001942.git.liliana.prikler@gmail.com> (Liliana Marie Prikler's message of "Wed, 2 Aug 2023 20:30:11 +0200")
Hi,
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> * gnu/packages/emacs.scm (emacs-minimal): Update to 29.1.
> [source]: Use url-fetch again.
Looking forward to it! What’s the status?
<https://qa.guix.gnu.org/issue/65000> shows that a lot has been built
already, though there are new failures on x86_64-linux.
> (define-public emacs-minimal
> (package
> (name "emacs-minimal")
> - (version "29.0.92")
> + (version "29.1")
Hmm on ‘master’ ‘emacs-minimal’ is at 28.2, not 29.0.92. What branch is
this?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-08-23 10:07 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
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 ` Ludovic Courtès [this message]
2023-08-23 12:13 ` [bug#65000] [PATCH] gnu: emacs-next: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7iy139m.fsf_-_@gnu.org \
--to=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.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.