From: Lukas Straub <lukasstraub2@web.de>
To: Eric Levy <contact@ericlevy.name>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: separate mailing list for patches?
Date: Tue, 15 Nov 2022 19:47:44 +0000 [thread overview]
Message-ID: <20221115194744.6a343639@gecko.fritz.box> (raw)
In-Reply-To: <0YIELR.GA2T7GBWR97P2@ericlevy.name>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
On Tue, 15 Nov 2022 13:20:24 -0500
Eric Levy <contact@ericlevy.name> wrote:
> 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.
>
>
>
By the way: You don't have to be subscribed to the mailing-list at all.
You can just send emails to linux-btrfs@vger.kernel.org. The implied
reply-policy on pretty much any mailing list is reply-to-all so if
anyone replies to you he will send with To: You and CC:
linux-btrfs@vger.kernel.org and also CC: anyone else involved in the
discussion so far (Thats what the Reply-to-all button in your mail
client does). So it just works without being subscribed.
Regards,
Lukas Straub
--
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-15 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:20 separate mailing list for patches? Eric Levy
2022-11-15 19:47 ` Lukas Straub [this message]
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=20221115194744.6a343639@gecko.fritz.box \
--to=lukasstraub2@web.de \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.