unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: RE: Three cheers for Eli!
Date: Tue, 29 May 2018 07:02:06 -0700 (PDT)	[thread overview]
Message-ID: <b05d8d69-fb36-47c2-b175-ed6c64b0237b@default> (raw)
In-Reply-To: <20180528174225.GA4316@ACM>

> Thanks to Nicolas for releasing Emacs 26.1.
> 
> But also massive thanks to Eli in particular.  The amount of work he's
> been putting into Emacs over many months is phenomenal, ranging from the
> trickiest of problems to the most mundane of bug reports.  Yes, Eli,
> we've noticed.  Thanks again!

+1



  parent reply	other threads:[~2018-05-29 14:02 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 17:42 Three cheers for Eli! Alan Mackenzie
2018-05-28 18:17 ` Eli Zaretskii
2018-05-28 19:39 ` Clément Pit-Claudel
2018-05-28 20:29   ` John Wiegley
2018-05-30 10:29     ` Van L
2018-05-28 19:45 ` Óscar Fuentes
2018-05-29  1:30 ` Stefan Monnier
2018-05-29 13:52   ` T.V Raman
2018-05-29  3:10 ` Richard Stallman
2018-05-29 16:54   ` Eli Zaretskii
2018-05-29 18:02     ` George Plymale II
2018-05-30  7:04       ` Tim Cross
2018-05-30 10:53         ` Basil L. Contovounesios
2018-06-03 18:29       ` Jefferson Carpenter
2018-05-29 14:02 ` Drew Adams [this message]
2018-05-29 14:40   ` Rostislav Svoboda
2018-05-29 15:10     ` Gian Uberto Lauri
2018-05-30  7:23 ` Andreas Röhler
2018-05-30  8:15   ` Boruch Baum
2018-05-30 10:56 ` Dmitry Gutov
2018-05-31 15:59   ` Kaushal Modi
2018-05-31 22:57     ` John Yates
2018-06-01  8:09       ` Eli Zaretskii
2018-06-01  3:02     ` Richard Stallman
2018-06-01 14:02       ` John Yates
2018-06-02  3:29         ` Richard Stallman
2018-06-02 12:30           ` John Yates
2018-06-03  2:32             ` Richard Stallman
2018-06-03 14:58               ` Eli Zaretskii
2018-06-04  4:16                 ` Richard Stallman
2018-06-04  4:47                 ` Marcin Borkowski
2018-06-04  5:09                   ` Amin Bandali
2018-06-04  8:30                     ` Marcin Borkowski
2018-06-04  8:53                       ` Van L
2018-06-04 15:49                       ` Eli Zaretskii
2018-06-07 17:05                         ` Marcin Borkowski
2018-06-07 18:00                           ` João Távora
2018-06-11  3:25                             ` Marcin Borkowski
2018-06-11 13:50                               ` Joshua Branson
2018-06-12  0:35                                 ` Richard Stallman
2018-06-12  0:33                               ` Richard Stallman
2018-06-15 17:00                                 ` Marcin Borkowski
2018-06-15 17:44                                   ` Clément Pit-Claudel
2018-06-15 18:03                                     ` Marcin Borkowski
2018-06-15 18:10                                       ` João Távora
2018-06-04 23:29                       ` Richard Stallman
2018-06-07 17:06                         ` Marcin Borkowski

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=b05d8d69-fb36-47c2-b175-ed6c64b0237b@default \
    --to=drew.adams@oracle.com \
    --cc=acm@muc.de \
    --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).