From: Eric Levy <contact@ericlevy.name>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: separate mailing list for patches?
Date: Tue, 15 Nov 2022 15:01:29 -0500 [thread overview]
Message-ID: <HMNELR.D0MZMRGVI0JI2@ericlevy.name> (raw)
In-Reply-To: <4f3526771aa69fe275693aaa07e98e8e12452e99.camel@scientia.org>
On Tue, Nov 15 2022 at 08:56:53 PM +0100, Christoph Anton Mitterer
<calestyo@scientia.org> wrote:
> This however has also it's downsides (in particular for the users):
> namely likely less attention by the developers ;-)
Yes, if the developers subscribe only to one, and use it for all
communication among themselves. As was my intended suggestion, I
thought it might be helpful broadly, though perhaps very slightly less
convenient for some, to put the patches on a dedicated channel,
separate from one for the regular messages, containing written text for
any purpose.
prev parent reply other threads:[~2022-11-15 20:01 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
2022-11-15 20:01 ` Eric Levy [this message]
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=HMNELR.D0MZMRGVI0JI2@ericlevy.name \
--to=contact@ericlevy.name \
--cc=calestyo@scientia.org \
--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.