From: Andrew Tropin <andrew@trop.in>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, 63984@debbugs.gnu.org
Cc: liliana.prikler@gmail.com
Subject: [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29
Date: Sat, 10 Jun 2023 10:46:39 +0400 [thread overview]
Message-ID: <87ilbv95m8.fsf@trop.in> (raw)
In-Reply-To: <cover.1686327727.git.liliana.prikler@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
On 2023-06-09 18:22, Liliana Marie Prikler wrote:
> Hi Guix,
>
> it's already been four weeks since the newest Emacs pre-release. Time
> sure flies. With that in mind, I'd like to start work in the Emacs team
> focused on
> 1. streamlining our Emacs packages
> 2. improving emacs-build-system and adapting it to the new features of
> Emacs 29 (including the almost forgotten [1])
> 3. improving our Emacs package management (i.e. making it easier to
> declare variants of emacs-* packages built with different Emacsen)
>
> This series gets us started on (1), so we can do (2) and (3) hopefully
> soon.
>
> Cheers
>
> [1] https://issues.guix.gnu.org/57122
>
> Liliana Marie Prikler (2):
> gnu: Make emacs-next-tree-sitter the new emacs.
> gnu: Construct Emacs packages from bottom up.
>
> gnu/local.mk | 1 -
> gnu/packages/emacs.scm | 467 +++++++-----------
> .../patches/emacs-source-date-epoch.patch | 20 -
> 3 files changed, 190 insertions(+), 298 deletions(-)
> delete mode 100644 gnu/packages/patches/emacs-source-date-epoch.patch
>
>
> base-commit: 44bbfc24e4bcc48d0e3343cd3d83452721af8c36
Hi Liliana,
the patch series looks good, thank you for working on this. Do we want
to add (define-deprecated/alias) to make the transition to new emacs
package names smoother?
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-06-10 6:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 16:22 [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 Liliana Marie Prikler
2023-06-09 8:40 ` [bug#63984] [PATCH emacs-team 1/2] gnu: Make emacs-next-tree-sitter the new emacs Liliana Marie Prikler
2023-06-09 11:28 ` [bug#63984] [PATCH emacs-team 2/2] gnu: Construct Emacs packages from bottom up Liliana Marie Prikler
2023-06-10 6:46 ` Andrew Tropin [this message]
2023-06-10 7:46 ` [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 Liliana Marie Prikler
2023-06-10 8:20 ` Andrew Tropin
2023-06-10 8:51 ` Liliana Marie Prikler
2023-06-11 5:35 ` Andrew Tropin
2023-06-11 21:09 ` Mekeor Melire
2023-06-12 4:30 ` Andrew Tropin
2023-07-04 7:39 ` Mekeor Melire
2023-07-08 17:04 ` Liliana Marie Prikler
2023-07-12 18:15 ` Mekeor Melire
2023-07-13 16:20 ` bug#63984: " 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=87ilbv95m8.fsf@trop.in \
--to=andrew@trop.in \
--cc=63984@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
/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).