From: Eli Zaretskii <eliz@gnu.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-devel@gnu.org
Subject: Re: Releasing Emacs 26.1
Date: Tue, 08 May 2018 05:28:07 +0300 [thread overview]
Message-ID: <83tvriq3t4.fsf@gnu.org> (raw)
In-Reply-To: <87r2mn6rys.fsf@gmx.us> (message from Rasmus on Tue, 08 May 2018 00:06:35 +0200)
> From: Rasmus <rasmus@gmx.us>
> Date: Tue, 08 May 2018 00:06:35 +0200
>
> Here’s a full list of the changes not merged, with a detailed changelog
> attached. I am not really sure how to "pick" changes to port. But as I
> wrote in another message, will it be able to add these to a subsequent
> minor release (26.1.1, say?)
That would be 26.2, and yes, bugfixes will be welcome on the emacs-26
branch after 26.1 release.
next prev parent reply other threads:[~2018-05-08 2:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 19:52 Releasing Emacs 26.1 Eli Zaretskii
2018-05-06 21:00 ` Alan Third
2018-05-07 1:21 ` Basil L. Contovounesios
2018-05-07 12:31 ` Alan Third
2018-05-07 12:46 ` Basil L. Contovounesios
2018-05-07 17:42 ` Eli Zaretskii
2018-05-07 0:13 ` Phil Sainty
2018-05-07 7:32 ` Michael Albinus
2018-05-07 11:10 ` Phil Sainty
2018-05-07 11:29 ` Michael Albinus
2018-05-07 15:08 ` Nicolas Petton
2018-05-07 18:09 ` Eli Zaretskii
2018-05-07 11:44 ` Van L
2018-05-07 12:05 ` Bastien
2018-05-07 18:08 ` Eli Zaretskii
2018-05-07 17:44 ` Eli Zaretskii
2018-05-07 5:30 ` John Wiegley
2018-05-07 5:40 ` Bastien
2018-05-07 19:05 ` Eli Zaretskii
2018-05-07 22:06 ` Rasmus
2018-05-08 2:28 ` Eli Zaretskii [this message]
2018-05-08 7:06 ` Byung-Hee HWANG (황병희, 黃炳熙)
2018-05-20 13:56 ` Alan Mackenzie
2018-05-20 15:48 ` Eli Zaretskii
2018-05-20 19:14 ` Alan Mackenzie
2018-05-21 9:25 ` Nicolas Petton
2018-05-22 7:38 ` Tino Calancha
2018-05-22 9:40 ` Van L
2018-05-22 9:56 ` Van L
2018-05-24 1:40 ` Van L
2018-05-25 5:10 ` Tino Calancha
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=83tvriq3t4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rasmus@gmx.us \
/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).