From: Randy Dunlap <rdunlap@infradead.org>
To: NeilBrown <neilb@suse.de>, Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Andrew Morton <akpm@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: Wed, 25 Oct 2023 15:00:01 -0700 [thread overview]
Message-ID: <81685f3d-b130-4c09-a29e-56cc5235ac25@infradead.org> (raw)
In-Reply-To: <169826846576.20306.981035382886610843@noble.neil.brown.name>
On 10/25/23 14:14, NeilBrown wrote:
> On Wed, 25 Oct 2023, Geert Uytterhoeven wrote:
>> Hi Neil,
>>
>> On Tue, Oct 24, 2023 at 11:29 PM NeilBrown <neilb@suse.de> wrote:
>>> On Wed, 25 Oct 2023, Krzysztof Kozlowski wrote:
>>>> On 23/10/2023 20:49, Andrew Morton wrote:
>>>>> On Thu, 19 Oct 2023 07:11:36 +0300 Dan Carpenter <dan.carpenter@linaro.org> wrote:
>>>>>> Yesterday someone on my lists just sent an email looking for kernel
>>>>>> tasks.
>>>>>
>>>>> 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.
>>>>>
>>>>> It's happening significantly more lately. Possibly because the gmail
>>>>> client helpfully hides quoted text.
>>>>
>>>> I would also point to reviewers and maintainers who give a Rb/Ack tag:
>>>> 1. somewhere at the top, without any footer like Best regards, and then
>>>> quote entire patch, so I don't know shall I look for more comments after
>>>> Rb/Ack?
>>>>
>>>> 2. quote entire email and then add Rb/Ack, so I need to figure out
>>>> whether there was something between the hundreds of lines of text or not.
>>>
>>> Here we all are, brilliantly talented computer programmers who spend
>>> our days making amazing fast digital devices do amazingly clever and
>>> subtle things, inventing time-saving tools and processing vast amounts
>>> of data without blinking, but for some reason we think the task of
>>> skipping over a few thousand lines that all start with '> " is too hard
>>> for us and that we should, in stead, complain to some other human to
>>> convince them to make our life easier for us.
>>>
>>> Does anyone else see the irony?
>>
>> Please compare the numbers:
>> 1. 1 sender removes irrelevant parts,
>> 2. N receivers skip irrelevant parts.
>
> That is one way to look at the numbers.
> Another is:
>
> 12 - fix about a dozen MUAs to summaries quotes properly
> 12000 - fix an unknownable number of people to quote just exactly the
> amount that their particular audience is going to want
>
> and when it comes to fixing-code versus fixing-people, I know which this
> community is better at.
>
> I guess there is also the option
>
> 1 - fix vger.kernel.org to reject postings from people who don't
> think and quote like "us", because we already have too many
> contributor and want to block the heretics
>
> This is really just a form of the "platform problem" which lwn.net has
> occasionally written about. The "problem" is that we treat the platform
> (library code or other infrastructure) as fixed and develop ugly hacks
> in our own code to work around some shortcoming, rather the going into
> the platform and fixing it once for everyone there.
The problem AFAICT is that many (most?) of us expect a certain level of
etiquette but we are not seeing it in some posts.
--
~Randy
next prev parent reply other threads:[~2023-10-25 22:00 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
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 [this message]
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=81685f3d-b130-4c09-a29e-56cc5235ac25@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@linaro.org \
--cc=geert@linux-m68k.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=neilb@suse.de \
--cc=outreachy@lists.linux.dev \
/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