unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@librehacker.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 emacs-devel@gnu.org, emacsconf-discuss@gnu.org
Subject: Re: Emacs 30 Release?
Date: Mon, 26 Aug 2024 09:01:35 -0800	[thread overview]
Message-ID: <87zfozfcb4.fsf@librehacker.com> (raw)
In-Reply-To: <CADwFkmm0yS_UFS88WBs9TijyEEio2sY3dj8rhX5GeckxY5ioeg@mail.gmail.com> (Stefan Kangas's message of "Fri, 23 Aug 2024 22:41:46 +0000")

Stefan Kangas <stefankangas@gmail.com> writes:
> Yes, the branch you want is emacs-30.  I'd recommend doing that,
> especially if time is concern.
>

I just built it this morning from the emacs-30 repo branch. I am using guix's emacs-next environment, and did not have any trouble building or installing it. I just have to set the EMACSLOADPATH to the correct place, and also keep a watch on what info files I'm loading, so I'm reading the newer manuals. Thanks!

I was expecting half my code to break, or something. But undramatically, my entire init.el loaded normally without any errors or warnings. A seamless experience so far...

-- 
Christopher Howard



  reply	other threads:[~2024-08-26 17:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 21:43 Emacs 30 Release? Christopher Howard
2024-08-22  3:50 ` Eli Zaretskii
2024-08-22 16:35   ` Christopher Howard
2024-08-22 16:56     ` : " Robert Pluim
2024-08-22 17:24     ` Juergen Fenn
2024-08-22 17:49     ` Eli Zaretskii
2024-08-22 19:39       ` Christopher Howard
2024-08-23 22:41         ` Stefan Kangas
2024-08-26 17:01           ` Christopher Howard [this message]
2024-08-26 17:49             ` Eli Zaretskii
2024-08-28 15:21               ` Post-Upgrade Breakage Philip Kaludercic
2024-09-01 20:15               ` Emacs 30 Release? pinmacs
2024-09-01 20:24                 ` pinmacs
2024-09-02 11:20                 ` Eli Zaretskii

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfozfcb4.fsf@librehacker.com \
    --to=christopher@librehacker.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacsconf-discuss@gnu.org \
    --cc=stefankangas@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/emacs.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).