From: <tomas@tuxteam.de>
To: c.buhtz@posteo.jp
Cc: emacs-orgmode@gnu.org
Subject: Re: Reply-All noise
Date: Sat, 10 Oct 2020 11:05:26 +0200 [thread overview]
Message-ID: <20201010090526.GA25592@tuxteam.de> (raw)
In-Reply-To: <4C7dxx6Vq1z9rxS@submission02.posteo.de>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Sat, Oct 10, 2020 at 10:53:08AM +0200, c.buhtz@posteo.jp wrote:
> On 2020-10-10 15:03 Maxim Nikulin <manikulin@gmail.com> wrote:
> > 1. Use "duplicate" sieve extension.
> > [..]
> >
> > 2. Just add filter
> > [..]
>
> This are workarounds but not solutions.
>
> IMO the problem is the list user that "Answers to all".
"The problem are always the others". Way to go!
Did you read the reference I sent in reply to you? Did you take
into account that this list is open to non-subscribers?
> Why should I modify my system because another one make errors?
It's not "errors". It's the way an open mailing list works.
Entering a room and yelling "Hey, all of you stop doing things
the way you're doing it. I'm gonna tell ya how you gotta do
things now" is, to put it politely, slightly unpolite :-)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-10-10 9:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 19:24 Reply-All noise c.buhtz
2020-10-09 20:10 ` tomas
2020-10-09 20:41 ` tomas
2020-10-10 8:57 ` c.buhtz
2020-10-10 9:10 ` tomas
2020-10-10 10:45 ` c.buhtz
2020-10-10 14:40 ` Jens Lechtenboerger
2020-10-30 11:30 ` Russell Adams
2020-10-30 12:14 ` Eric S Fraga
2020-10-09 21:22 ` Tory S. Anderson
2020-10-10 8:03 ` Maxim Nikulin
2020-10-10 8:53 ` c.buhtz
2020-10-10 9:05 ` tomas [this message]
2020-10-10 13:57 ` Maxim Nikulin
2020-10-10 18:56 ` c.buhtz
2020-10-11 13:58 ` Eric S Fraga
2020-10-11 14:35 ` c.buhtz
2020-10-11 15:21 ` Eric S Fraga
2020-10-11 21:32 ` Tim Cross
2020-10-11 22:25 ` Eric Abrahamsen
2020-11-01 18:38 ` Anthony Carrico
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201010090526.GA25592@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=c.buhtz@posteo.jp \
--cc=emacs-orgmode@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/org-mode.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).