public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: WangYuli <wangyuli@uniontech.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] fs/pipe: Introduce a check to skip sleeping processes during pipe read/write
Date: Wed, 25 Dec 2024 17:56:38 +0100	[thread overview]
Message-ID: <20241225165638.GA12343@1wt.eu> (raw)
In-Reply-To: <9B33A2E79ADF512B+c7748c58-9b1c-4759-8131-1007c08e9f46@uniontech.com>

On Thu, Dec 26, 2024 at 12:32:35AM +0800, WangYuli wrote:
> Hi,
> 
> I've reviewed the Contributor Covenant and the Linux Kernel Contributor
> Covenant Code of Conduct Interpretation, and I couldn't find anything
> suggesting that CCing a large number of people is "unfriendly".

This is unrelated, it's a matter of basic social interactions and respect
of others' time.

> And while I don't believe my actions were malicious, I understand your
> concern.
> 
> Going forward, I'll be more considerate of the recipients when sending
> emails and will avoid CCing more than a hundred people at once in similar
> situations.

"More than a hundred" ? Are you serious ? For what purpose ? I'll explain
you something related to how people consume e-mails: the first thing they
do if they hesitate to process it is to check if someone else in the To
or Cc is more knowledgeable or legitimate than them. If so they often
prefer to let others deal with it. With such a large list, it's impossible
to check all other addresses and virtually *everyone* will consider that
surely one of the hundreds of others is more legitimate. So the more people
you add, the less likely anyone will handle your request.

The common rules that apply here are not made out of nowhere but based on
what works best. Just send to the most relevant outputs of get_maintainer,
wait for one week and if you get no response it's just that these people
were busy and forgot about you, so just kindly ping again to make sure
your message was received. With such a large community it's normal to lose
some messages, and pinging again is normally not considered as an offence
so that's fine. If you get no response after multiple attempts, it might
mean there's something annoying in your message (like sending to tens or
hundreds of people at once).

And really, when a script tells you "send your message to these 3 people"
and you send it to 191, how can you imagine the recipients will think
anything different from "this person feels super important to spam
everyone like this". Why would they even respond if they feel like you
consider you have the right to spam everyone in hope to get your orders
processed immediately ? I'm pretty sure that the majority will just let
it rot by principle.

Good luck,
Willy

  reply	other threads:[~2024-12-25 16:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  9:42 [RESEND PATCH] fs/pipe: Introduce a check to skip sleeping processes during pipe read/write WangYuli
2024-12-25 13:30 ` Andy Shevchenko
2024-12-25 13:53   ` Kent Overstreet
2024-12-25 16:04     ` Mateusz Guzik
2024-12-25 16:32       ` Kent Overstreet
2024-12-25 17:22         ` Mateusz Guzik
2024-12-25 17:41           ` Kent Overstreet
2024-12-25 15:42   ` WangYuli
2024-12-25 16:00     ` Willy Tarreau
2024-12-25 16:32       ` WangYuli
2024-12-25 16:56         ` Willy Tarreau [this message]
2024-12-26 16:00 ` Oleg Nesterov
2024-12-26 19:02 ` Linus Torvalds
2024-12-26 20:11   ` Oleg Nesterov
2024-12-26 20:29     ` Linus Torvalds
2024-12-26 20:57       ` Oleg Nesterov
2024-12-27 15:54         ` Oleg Nesterov
2024-12-27 16:43           ` Oleg Nesterov
2024-12-27 18:39     ` Manfred Spraul
2024-12-28 14:32       ` Oleg Nesterov
2024-12-28 15:22         ` Oleg Nesterov
2024-12-28 16:32           ` Oleg Nesterov
2024-12-28 18:53             ` Manfred Spraul
2024-12-29 11:54               ` Oleg Nesterov
2024-12-28 16:45           ` Manfred Spraul
2024-12-29 11:57             ` Oleg Nesterov
2024-12-29 12:41               ` Manfred Spraul
2024-12-29 13:05                 ` Oleg Nesterov
2024-12-29 13:13                   ` Oleg Nesterov
2024-12-29 19:54                     ` Manfred Spraul
2024-12-30 15:38                       ` Oleg Nesterov
2024-12-31 11:14                         ` Manfred Spraul
2024-12-31 19:38                           ` Linus Torvalds
2024-12-31 20:24                             ` Oleg Nesterov
2024-12-31 22:31                               ` Linus Torvalds
2025-01-02 13:57                                 ` Oleg Nesterov
2025-01-04 21:15                         ` RFC: Checkpatch: Introduce list of functions that need memory barriers Manfred Spraul

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=20241225165638.GA12343@1wt.eu \
    --to=w@1wt.eu \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangyuli@uniontech.com \
    /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