From: Eshel Yaron <me@eshelyaron.com>
To: emacs-devel@gnu.org
Subject: Blog post
Date: Thu, 14 Dec 2023 08:09:07 +0100 [thread overview]
Message-ID: <m15y11tg4s.fsf@dazzs-mbp.home> (raw)
Hi Emacs,
I recently wrote a post on my blog that criticized a certain development
in Emacs, and I think I owe some people here an apology, in particular,
Eli and Thierry. I never expected that rant to spread so widely
(somebody posted it on HN IIUC), and I was wrong to be so harsh. I'm sorry.
I hope to continue contributing to Emacs and its community, and to keep
such ranting to myself.
Regards,
Eshel
next reply other threads:[~2023-12-14 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 7:09 Eshel Yaron [this message]
2023-12-14 7:56 ` Blog post Christopher Dimech
2023-12-14 8:30 ` Dr. Arne Babenhauserheide
2023-12-14 9:22 ` Christopher Dimech
2023-12-14 9:29 ` Dr. Arne Babenhauserheide
2023-12-14 9:33 ` Eli Zaretskii
2024-01-10 23:14 ` Stefan Kangas
2024-01-11 9:26 ` Eshel Yaron
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=m15y11tg4s.fsf@dazzs-mbp.home \
--to=me@eshelyaron.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).