From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs 26.1 release soon? :-)
Date: Wed, 26 Jul 2017 18:44:55 +0300 [thread overview]
Message-ID: <m2vamfb3t4.fsf@lifelogs.com> (raw)
In-Reply-To: m3k22vl1au.fsf@stories
On Wed, 26 Jul 2017 16:28:57 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Unless I'm misremembering, the Emacs 26 branch has almost three years of
LI> fresh and exciting development in it by now (*counts years on fingers
LI> because he can't convince git to couch up the data*), so isn't it about
LI> time to start thinking about pushing Emacs 26.1 out the door?
You mean Emacs 2017? :P
Ted
next prev parent reply other threads:[~2017-07-26 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 14:28 Emacs 26.1 release soon? :-) Lars Ingebrigtsen
2017-07-26 14:41 ` Michael Albinus
2017-07-26 22:12 ` Lars Ingebrigtsen
2017-07-27 6:46 ` Michael Albinus
2017-07-26 15:44 ` Ted Zlatanov [this message]
2017-07-27 13:20 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-07-27 17:17 ` Lars Ingebrigtsen
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=m2vamfb3t4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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 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).