From: Randy Dunlap <rdunlap@infradead.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org
Subject: Re: lore+lei: getting started
Date: Sun, 7 Nov 2021 18:17:30 -0800 [thread overview]
Message-ID: <de0e373c-cd96-752c-ceea-04c7a485280a@infradead.org> (raw)
In-Reply-To: <lorelei.part1.202111051304.mdtebsxahljcrxak@meerkat.local>
On 11/5/21 10:07 AM, Konstantin Ryabitsev wrote:
> For this reason, actual Linux development tends to happen on separate mailing
> lists dedicated to each particular subsystem. In turn, this has several
> negative side-effects:
>
> 1. Developers working across multiple subsystems end up needing to subscribe
> to many different mailing lists in order to stay aware of what is happening
> in each area of the kernel.
>
> 2. Contributors submitting patches find it increasingly difficult to know
> where to send their work, especially if their patches touch many different
> subsystems.
3. Users send email problem reports to LKML they are completely ignored.
(They don't know better or they think that the big pipe must be useful for
something or whatever....)
--
~Randy
next prev parent reply other threads:[~2021-11-08 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 17:07 Konstantin Ryabitsev
2021-11-08 2:17 ` Randy Dunlap [this message]
2021-11-08 19:49 ` Rob Herring
[not found] ` <20211108202204.q5zg6bachnvbjlnx@meerkat.local>
2021-11-08 20:49 ` lei: incorrect quoting on saved searches (was Re: lore+lei: getting started) Eric Wong
2021-11-08 21:36 ` Konstantin Ryabitsev
2021-11-08 21:48 ` Eric Wong
2021-11-08 22:36 ` Konstantin Ryabitsev
2021-11-08 22:57 ` Eric Wong
2022-01-10 19:40 ` lore+lei: getting started Bjorn Helgaas
2022-01-11 1:52 ` Kyle Meyer
2022-03-07 16:48 ` Rob Herring
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=de0e373c-cd96-752c-ceea-04c7a485280a@infradead.org \
--to=rdunlap@infradead.org \
--cc=konstantin@linuxfoundation.org \
--cc=workflows@vger.kernel.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