From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 61513@debbugs.gnu.org
Cc: Jelle Licht <jlicht@fsfe.org>
Subject: bug#61513: [PATCH 2/2] gnu: emacs-next: Update to 29.0.60-1.f1f571e.
Date: Thu, 16 Feb 2023 21:45:24 +0100 [thread overview]
Message-ID: <4c405dcf2c0059204664c1f6f659e175b3fe2776.camel@gmail.com> (raw)
In-Reply-To: <87r0us0yvu.fsf@fsfe.org>
* gnu/packages/emacs.scm (emacs-next): Update to 29.0.60-1.f1f571e.
---
Note: Haven't tried to build the commit yet, but the hash checks out.
gnu/packages/emacs.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index e230fdc84d..51ce4e481b 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -391,8 +391,8 @@ (define* (emacs-byte-compile-directory dir)
(license license:gpl3+)))
(define-public emacs-next
- (let ((commit "ac7ec87a7a0db887e4ae7fe9005aea517958b778")
- (revision "0"))
+ (let ((commit "f1f571e72ae10285762d3a941e56f7c4048272af")
+ (revision "1"))
(package
(inherit emacs)
(name "emacs-next")
@@ -411,7 +411,7 @@ (define-public emacs-next
"emacs-native-comp-driver-options.patch"))
(sha256
(base32
- "1akq6dbllwwqwx21wnwnv6aax1nsi2ypbd7j3i79sw62s3gf399z"))))
+ "1rildbxq53yvc2rllg2qccgxzbbnr6qbija0lyqacsy8dlzaysch"))))
(inputs
(modify-inputs (package-inputs emacs)
(prepend sqlite)))
--
2.39.1
prev parent reply other threads:[~2023-02-16 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 20:34 bug#61513: emacs-next@29.0.60 self-reports as version 30.0.50 Jelle Licht
2023-02-16 20:36 ` bug#61513: [PATCH 1/2] gnu: Add emacs-next-tree-sitter Liliana Marie Prikler
2023-02-20 10:33 ` Simon Tournier
2023-02-20 19:21 ` Liliana Marie Prikler
2023-02-21 12:38 ` Simon Tournier
2023-02-26 8:25 ` Liliana Marie Prikler
2023-02-16 20:45 ` Liliana Marie Prikler [this message]
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=4c405dcf2c0059204664c1f6f659e175b3fe2776.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=61513@debbugs.gnu.org \
--cc=jlicht@fsfe.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 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).