From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3D3DDC433FE for ; Tue, 15 Nov 2022 19:53:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230387AbiKOTxG (ORCPT ); Tue, 15 Nov 2022 14:53:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46052 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229940AbiKOTxE (ORCPT ); Tue, 15 Nov 2022 14:53:04 -0500 Received: from zmcc-3-mx.zmailcloud.com (zmcc-3-mx.zmailcloud.com [34.200.143.36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AB28962D6 for ; Tue, 15 Nov 2022 11:53:01 -0800 (PST) Received: from zmcc-3.zmailcloud.com (183.87.154.104.bc.googleusercontent.com [104.154.87.183]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zmcc-3-mx.zmailcloud.com (Postfix) with ESMTPS id DD22B404FA; Tue, 15 Nov 2022 13:56:53 -0600 (CST) Received: from zmcc-3.zmailcloud.com (localhost [127.0.0.1]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTPS id AD4038036FCB; Tue, 15 Nov 2022 13:53:00 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTP id 9CDB98036FDA; Tue, 15 Nov 2022 13:53:00 -0600 (CST) Received: from zmcc-3.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-3-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IEz6vKWV9hum; Tue, 15 Nov 2022 13:53:00 -0600 (CST) Received: from [10.4.2.11] (unknown [37.19.198.182]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTPSA id 1B9858036FCB; Tue, 15 Nov 2022 13:52:59 -0600 (CST) Date: Tue, 15 Nov 2022 14:52:52 -0500 From: Eric Levy Subject: Re: separate mailing list for patches? To: Lukas Straub Cc: linux-btrfs Message-Id: <48NELR.GD3GOBQRO8OC3@ericlevy.name> In-Reply-To: <20221115194744.6a343639@gecko.fritz.box> References: <0YIELR.GA2T7GBWR97P2@ericlevy.name> <20221115194744.6a343639@gecko.fritz.box> X-Mailer: geary/40.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Tue, Nov 15 2022 at 07:47:44 PM +0000, Lukas Straub wrote: > On Tue, 15 Nov 2022 13:20:24 -0500 > Eric Levy 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 > > -- Thank you for the extremely useful information. I have not been following the policy, and also, probably was also carrying an assumption that messages are only accepted from subscribers, as I think is the policy on some lists, perhaps to control spam and trolling. At any rate, perhaps some subscribers have the preference for not receiving patches, and might appreciate my idea, but I will be happy simply to use the list following in the way you suggest.