From: Amin Bandali <bandali@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Emacs 27
Date: Wed, 18 Dec 2019 15:32:54 -0500 [thread overview]
Message-ID: <8736dhz85l.fsf@gnu.org> (raw)
In-Reply-To: <C39BAAE1-FE37-43E6-BEF8-47D8A5EEBB37@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
Hi John,
John Soo <jsoo1@asu.edu> writes:
> Hi guix,
>
> Speaking of the next version of emacs, do you think we could add an
> emacs-next package? I have tried to build from head recently and the
> recent changes to the dumping mechanism does not work with our current
> package definition.
>
> - John
Perfect timing? :-) https://issues.guix.gnu.org/issue/38662
-amin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2019-12-18 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 18:51 Emacs 27 John Soo
2019-12-18 20:32 ` Amin Bandali [this message]
2019-12-18 22:48 ` John Soo
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=8736dhz85l.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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).