From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: status of emacs-25 branch
Date: Wed, 10 May 2017 18:47:05 +0100 [thread overview]
Message-ID: <87mvakppt2.fsf@russet.org.uk> (raw)
In-Reply-To: <83fugdbfzj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 May 2017 05:30:40 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: emacs-devel@gnu.org
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Tue, 9 May 2017 12:16:24 -0700
>>
>> On 05/09/2017 10:47 AM, Eli Zaretskii wrote:
>> > As for merging to master, I think I saw Paul doing that recently.
>>
>> As I recall, I did that after 25.2 was released, and wasn't planning to
>> do it later unless there's a real need.
>
> I don't expect to see a significant amount of changes to the branch,
> so I believe you are right.
Is the bigger question not, what is the status of master?
If Emacs-25 is bug release only, should when is the emacs-26 branch
coming.
Phil
next prev parent reply other threads:[~2017-05-10 17:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 17:06 status of emacs-25 branch Glenn Morris
2017-05-09 17:47 ` Eli Zaretskii
2017-05-09 19:16 ` Paul Eggert
2017-05-10 2:30 ` Eli Zaretskii
2017-05-10 17:47 ` Phillip Lord [this message]
2017-05-10 18:39 ` Eli Zaretskii
2017-05-21 15:37 ` John Wiegley
2017-05-21 16:03 ` Eli Zaretskii
2017-05-21 17:39 ` Michael Albinus
2017-05-21 18:39 ` Eli Zaretskii
2017-05-22 7:39 ` Michael Albinus
2017-05-22 18:43 ` Eli Zaretskii
2017-05-27 12:04 ` Eli Zaretskii
2017-05-29 21:04 ` Paul Eggert
2017-05-21 20:38 ` Nicolas Petton
2017-05-22 4:04 ` Eli Zaretskii
2017-05-22 15:45 ` martin rudalics
2017-05-22 20:03 ` John Wiegley
2017-05-24 18:14 ` Eli Zaretskii
2017-05-12 8:06 ` Eli Zaretskii
2017-05-15 1:09 ` Glenn Morris
2017-05-15 2:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvakppt2.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.