unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Misleading messages about new versions
Date: Mon, 14 Feb 2022 22:11:06 +0300	[thread overview]
Message-ID: <YgqpSn6I2BSi+c+z@protected.localdomain> (raw)
In-Reply-To: <877d9xtl2e.fsf@turtle-trading.net>

* Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net> [2022-02-14 20:28]:
> Hi Richard,
> 
> Richard Stallman writes:
> > For a new package, it could say,
> >
> >   We're glad to announce adding the new package Whatsit to XXGNU ELPA.
> >   The initial version number is X.Y.  Here's what Whatsit does:
> 
> Careful, a machine (program) that pretends to have feelings is a spam
> generator in my book.  I would not subscribe to such a bot on principle.

Somebody was behind the origination of communication. An original
author did write "We're glad to announce...". And Emacs users and
developers are really glad to expand software for Emacs. Aren't we?

When reading a book, one reads what original author intended. Even
though author could be dead, or not existent. Authors of books will
often put many of their personal feelings and observations of other
people's feelings into written stories. That some time passed after
receiving the communication is clear. 

A book written by author could be real or imaginary. Both types could
be very moving. 

Apart from that, intention of notices is to tell which package is
there as new and that it shall be announced. 

Package reviews are welcome. Everybody is free to write reviews and
send us announcements.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2022-02-14 19:11 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
2022-02-14 19:11       ` Jean Louis [this message]
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=YgqpSn6I2BSi+c+z@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=b.riefenstahl@turtle-trading.net \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).