From: Christoph Anton Mitterer <calestyo@scientia.org>
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 20:56:53 +0100 [thread overview]
Message-ID: <4f3526771aa69fe275693aaa07e98e8e12452e99.camel@scientia.org> (raw)
In-Reply-To: <48NELR.GD3GOBQRO8OC3@ericlevy.name>
On Tue, 2022-11-15 at 14:52 -0500, Eric Levy wrote:
> At any rate, perhaps some subscribers have the preference for not
> receiving patches, and might appreciate my idea
While I cannot speak for the developers, I'd guess they'd want to keep
*this* one as the development list, and rather have a separate user
list (if at all).
This however has also it's downsides (in particular for the users):
namely likely less attention by the developers ;-)
Cheers,
Chris.
next prev parent reply other threads:[~2022-11-15 19:57 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
2022-11-15 19:52 ` Eric Levy
2022-11-15 19:56 ` Christoph Anton Mitterer [this message]
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=4f3526771aa69fe275693aaa07e98e8e12452e99.camel@scientia.org \
--to=calestyo@scientia.org \
--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.