unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>,
	Michael Albinus <michael.albinus@gmx.de>,
	martin rudalics <rudalics@gmx.at>
Cc: jwiegley@gmail.com, "Francesco Potortì" <pot@gnu.org>,
	phillip.lord@russet.org.uk, rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: status of emacs-25 branch
Date: Mon, 29 May 2017 14:04:33 -0700	[thread overview]
Message-ID: <55dc95c5-fdee-24a5-4317-29b80b555f4f@cs.ucla.edu> (raw)
In-Reply-To: <837f12ijzq.fsf@gnu.org>

Eli Zaretskii wrote:
> It sounds like there will be no Emacs 25.3, so there's no need to
> back-port these to the emacs-25 branch.

OK, I marked Bug#26952 as found in 25.2 and fixed in 26.1, and closed the bug 
report.



  reply	other threads:[~2017-05-29 21:04 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
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 [this message]
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

  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=55dc95c5-fdee-24a5-4317-29b80b555f4f@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=michael.albinus@gmx.de \
    --cc=phillip.lord@russet.org.uk \
    --cc=pot@gnu.org \
    --cc=rgm@gnu.org \
    --cc=rudalics@gmx.at \
    /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).