From: John Wiegley <johnw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Releasing Emacs 26.1
Date: Sun, 06 May 2018 22:30:19 -0700 [thread overview]
Message-ID: <m2zi1cnic4.fsf@newartisans.com> (raw)
In-Reply-To: <83o9hsr28g.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 06 May 2018 22:52:15 +0300")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> Any objections to releasing Emacs 26.1 in a week's time, anyone?
None at all! Congrats.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2018-05-07 5:30 UTC|newest]
Thread overview: 33+ 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 13:24 ` comment alignment not lining up / C++//l OrgSrc Abbrev / " Van L
2018-05-18 11:10 ` SRC block with `-i' switch seems to solve the problem (was: comment alignment not lining up / C++//l OrgSrc Abbrev / Releasing Emacs 26.1) Van L
2018-05-07 18:08 ` Releasing Emacs 26.1 Eli Zaretskii
2018-05-07 17:44 ` Eli Zaretskii
2018-05-07 5:30 ` John Wiegley [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zi1cnic4.fsf@newartisans.com \
--to=johnw@gnu.org \
--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 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.