From: Andrew Morton <akpm@linux-foundation.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
ksummit@lists.linux.dev, outreachy@lists.linux.dev,
kernel-janitors@vger.kernel.org
Subject: Re: KTODO automated TODO lists
Date: Mon, 23 Oct 2023 21:58:39 -0700 [thread overview]
Message-ID: <20231023215839.bb712e78fec6a6e0c3e6b62f@linux-foundation.org> (raw)
In-Reply-To: <20231023-righteous-peridot-parakeet-1bbda0@meerkat>
On Mon, 23 Oct 2023 15:41:48 -0400 Konstantin Ryabitsev <mricon@kernel.org> wrote:
> On Mon, Oct 23, 2023 at 08:55:56AM -1000, Linus Torvalds wrote:
> > > Well here's a task: write a bot which follows the mailing lists and
> > > sends people nastygrams if one of their emails is more than 95%(?)
> > > quoted text.
> >
> > I think that might be better off as a spam filter rule.
> >
> > Don't make it some after-the-fact "trawl the lists". Just make it a
> > bounce with a "you quoted too much". Same as the html avoidance.
>
> I know people aren't being very serious, but automating this away either
> aggressively (reject as spam) or passive-agressively (whine at poster) will
> run into rare but valid corner cases. For example, we have no way of
> distinguishing between "this person quoted too much from previous message" and
> "this person posted a large but relevant quote from docs or another
> conversation," and so we will likely punish/annoy the innocent.
Rejecting a legtimate email would be bad.
So we choose "whine at poster". If it's a false positive then they'll
somehow survive the experience. And, most importantly, the mail
will get through.
> It's better to treat this as a mentoring opportunity and send an off-list
> reply with "please trim your quotes" and maybe a link to
> https://people.kernel.org/tglx/notes-about-netiquette
I'm tiring of sending off-list emails. This task could be automated.
Which is what I'm suggesting!
> If it helps, I can add a mailing list etiquette page on subspace.kernel.org,
> so it's easier to find.
Great, link to that in the whiney emails.
next prev parent reply other threads:[~2023-10-24 4:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 4:11 Dan Carpenter
2023-10-19 12:50 ` Linus Walleij
2023-10-19 13:21 ` Geert Uytterhoeven
2023-10-19 15:43 ` Liam R. Howlett
2023-10-19 16:30 ` Bird, Tim
2023-10-19 17:34 ` Dan Carpenter
2023-10-19 17:37 ` Bird, Tim
2023-10-19 17:47 ` Konstantin Ryabitsev
2023-10-23 18:49 ` Andrew Morton
2023-10-23 18:55 ` Linus Torvalds
2023-10-23 19:00 ` Geert Uytterhoeven
2023-10-23 19:17 ` Linus Torvalds
2023-10-23 19:29 ` Steven Rostedt
2023-10-23 21:31 ` Paul E. McKenney
2023-10-23 21:44 ` Tony Luck
2023-10-23 22:25 ` Paul E. McKenney
2023-10-23 19:41 ` Konstantin Ryabitsev
2023-10-24 4:58 ` Andrew Morton [this message]
2023-10-24 15:28 ` Konstantin Ryabitsev
2023-10-26 21:58 ` Miguel Ojeda
2023-10-23 21:45 ` NeilBrown
2023-10-24 7:19 ` Geert Uytterhoeven
2023-10-24 7:25 ` Laurent Pinchart
2023-10-24 8:42 ` Jani Nikula
2023-10-24 8:52 ` Laurent Pinchart
2023-10-24 12:36 ` Steven Rostedt
2023-10-24 13:12 ` Laurent Pinchart
2023-10-24 15:53 ` Krzysztof Kozlowski
2023-10-24 21:29 ` NeilBrown
2023-10-24 22:05 ` Steven Rostedt
2023-10-25 3:47 ` Paul E. McKenney
2023-10-25 23:45 ` Steven Rostedt
2023-10-25 6:55 ` Geert Uytterhoeven
2023-10-25 21:14 ` NeilBrown
2023-10-25 22:00 ` Randy Dunlap
2023-10-26 4:29 ` Dan Carpenter
2023-10-26 6:56 ` Geert Uytterhoeven
2023-10-25 7:01 ` Krzysztof Kozlowski
2023-10-25 11:45 ` James Bottomley
2023-10-25 16:40 ` Jani Nikula
2023-10-25 18:07 ` James Bottomley
2023-10-25 18:10 ` Steven Rostedt
2023-10-25 19:43 ` Linus Torvalds
2023-10-25 21:19 ` NeilBrown
2023-10-25 21:17 ` NeilBrown
2023-10-25 18:55 ` Alexey Dobriyan
2023-10-25 19:27 ` Steven Rostedt
2023-10-25 20:03 ` Alexandre Belloni
2023-10-25 21:38 ` NeilBrown
2023-10-23 23:38 ` Gustavo A. R. Silva
2023-10-24 0:07 ` Gustavo A. R. Silva
2023-10-24 2:16 ` Joe Perches
2023-12-11 18:47 ` Steven Rostedt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231023215839.bb712e78fec6a6e0c3e6b62f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=mricon@kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=torvalds@linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox