From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: Corwin Brust <corwin@bru.st>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Misleading messages about new versions
Date: Mon, 14 Feb 2022 19:44:11 +0100 [thread overview]
Message-ID: <87zgmts2ys.fsf@turtle-trading.net> (raw)
In-Reply-To: <CAJf-WoRc+q+yJvwbqtcN5bU-NwYfXumwU5uVgavN6yFpCwH7iQ@mail.gmail.com> (Corwin Brust's message of "Mon, 14 Feb 2022 12:31:27 -0600")
Hi Corwin,
Corwin Brust writes:
> Respectfully, I consider this caution misguided as applied to the
> quotation you kept.
Thanks for considering this in so much detail. I understand where this
is coming from, but it takes active reasoning for me to get there, and
in the end I still do not agree. Impressions and instinctive reactions
count and stuff like this is just off-putting to me. Maybe I'm too
sensitive.
I do not think there is more to say from my side.
so long, benny
next prev parent reply other threads:[~2022-02-14 18:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 3:57 Misleading messages about new versions Richard Stallman
2022-02-12 4:36 ` Stefan Monnier
2022-02-14 4:14 ` Richard Stallman
2022-02-14 12:47 ` Stefan Monnier
2022-02-14 17:27 ` Benjamin Riefenstahl
2022-02-14 18:31 ` Corwin Brust
2022-02-14 18:44 ` Benjamin Riefenstahl [this message]
2022-02-14 19:11 ` Jean Louis
2022-02-15 4:31 ` Richard Stallman
2022-02-14 4:14 ` How often do we have new packages in Whichever ELPA? Richard Stallman
2022-02-14 8:33 ` Philip Kaludercic
2022-02-15 4:30 ` Richard Stallman
2022-02-15 13:27 ` Eli Zaretskii
2022-02-16 4:14 ` Richard Stallman
2022-02-16 12:18 ` Eli Zaretskii
2022-02-16 10:42 ` Rudolf Schlatte
2022-02-19 4:54 ` Richard Stallman
2022-02-16 18:28 ` Tomas Hlavaty
2022-02-16 20:07 ` Philip Kaludercic
2022-02-19 4:56 ` Richard Stallman
2022-02-17 23:14 ` Richard Stallman
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=87zgmts2ys.fsf@turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--cc=corwin@bru.st \
--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).