unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: stefan@marxist.se, 46472@debbugs.gnu.org
Subject: bug#46472: Make lisp/mail/uce.el obsolete
Date: Thu, 04 Mar 2021 23:12:16 +0200	[thread overview]
Message-ID: <83sg5azkr3.fsf@gnu.org> (raw)
In-Reply-To: <1br1ku3eji.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 04 Mar 2021 14:27:29 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Cc: Stefan Kangas <stefan@marxist.se>,  46472@debbugs.gnu.org
> Date: Thu, 04 Mar 2021 14:27:29 -0500
> 
> Replying to spam is at best pointless, but most likely actively harmful.
> Emacs having a package to help you reply to spam is at best pointless,
> but most likely actively harmful.

Yes, Stefan already said that up-thread.  I don't see how our views on
what is and isn't appropriate response to spam should be mandatory for
the few users who may disagree.  This is free software, users are free
to do whatever they want with it.  Which is also something I already
said, so I don't see why do we need to reiterate the same arguments
without saying anything new.

> This is one of the many things that makes Emacs look antiquated.

Why "antiquated"?  Is there any other, more modern method we support
to respond to spam?

> I find the refusal to even obsolete such things demotivating for working
> on Emacs. So IMO the cost for keeping such things around is non-zero.

I sympathize with your feelings, but feelings aren't limited to one
side in a disagreement, and you are not the only one who finds this
and similar disputes demotivating.  Which is why I think we should try
to stay technical and not emotional.





  reply	other threads:[~2021-03-04 21:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 21:58 bug#46472: Make lisp/mail/uce.el obsolete Stefan Kangas
2021-02-13  7:58 ` Eli Zaretskii
2021-02-13 12:25   ` Stefan Kangas
2021-02-13 14:00     ` Eli Zaretskii
2021-03-04 19:27       ` Glenn Morris
2021-03-04 21:12         ` Eli Zaretskii [this message]
2021-03-06 17:14           ` Stefan Kangas
2021-03-06 17:25             ` Eli Zaretskii
2022-06-17 13:07         ` Lars Ingebrigtsen
2021-10-12  4:33       ` Stefan Kangas
2021-10-12 13:52         ` Eli Zaretskii
2021-10-12 16:12           ` Stefan Kangas
2021-10-12 16:44             ` Eli Zaretskii
2021-10-12 17:29               ` Stefan Kangas
2021-10-12 18:50                 ` Eli Zaretskii
2021-10-14 20:45                   ` Stefan Kangas
2021-10-15  6:12                     ` Eli Zaretskii
2021-10-15  8:50                       ` Stefan Kangas
2021-10-15 10:46                         ` Eli Zaretskii
2021-10-16 12:48                           ` Stefan Kangas
2021-10-16 12:50                             ` Eli Zaretskii
2021-10-17 23:56                               ` Stefan Kangas
2021-10-16 12:32                       ` Stefan Kangas
2021-03-03 21:22   ` Stefan Monnier
2021-03-04  3:39     ` Eli Zaretskii

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=83sg5azkr3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46472@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    --cc=stefan@marxist.se \
    /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).