From: Eric Levy <contact@ericlevy.name>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: separate mailing list for patches?
Date: Tue, 15 Nov 2022 13:20:24 -0500 [thread overview]
Message-ID: <0YIELR.GA2T7GBWR97P2@ericlevy.name> (raw)
I have subscribed to the Btrfs development list occasionally, for
seeking support and raising issues, though I am not involved in the
development effort. Currently, there is no channel of communication
more accessible to members of the public, yet, the list is often used
for patches sent among the development team. For many of us, it may
seem cumbersome to be flooded by so many messages carrying the patches.
Perhaps it would be useful to consider a separate mailing list for
patches, or to open a web interface that is friendly to those seeking
to interact with the group for more occasional support. Hopefully, it
would not much affect those regularly involved to subscribe to two
lists, using one for patches and the other for basic correspondence.
next reply other threads:[~2022-11-15 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:20 Eric Levy [this message]
2022-11-15 19:47 ` separate mailing list for patches? Lukas Straub
2022-11-15 19:52 ` Eric Levy
2022-11-15 19:56 ` Christoph Anton Mitterer
2022-11-15 20:01 ` Eric Levy
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=0YIELR.GA2T7GBWR97P2@ericlevy.name \
--to=contact@ericlevy.name \
--cc=linux-btrfs@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