From: Boris Buliga <boris@d12frosted.io>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 26.2
Date: Fri, 5 Oct 2018 20:15:16 +0300 [thread overview]
Message-ID: <CAD5F_-DV=LM8+kzdLvLR=ZuVKm9uvtS6sAoPZEEz5UH093jdWw@mail.gmail.com> (raw)
In-Reply-To: <831s943j34.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
Cool, looking forward!
On Fri, Oct 5, 2018 at 11:15 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Boris Buliga <boris@d12frosted.io>
> > Date: Thu, 4 Oct 2018 21:53:19 +0300
> >
> > Are there any plans for the new release of Emacs 26?
>
> Yes, I think we will start a pretest soon.
>
--
Cheers,
Boris
[-- Attachment #2: Type: text/html, Size: 797 bytes --]
next prev parent reply other threads:[~2018-10-05 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 18:53 Emacs 26.2 Boris Buliga
2018-10-05 8:15 ` Eli Zaretskii
2018-10-05 17:15 ` Boris Buliga [this message]
2018-10-05 17:28 ` John Wiegley
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='CAD5F_-DV=LM8+kzdLvLR=ZuVKm9uvtS6sAoPZEEz5UH093jdWw@mail.gmail.com' \
--to=boris@d12frosted.io \
--cc=eliz@gnu.org \
--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).