From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, tiwai@suse.de
Subject: Re: Migrating this list to a different platform (take 2)
Date: Thu, 19 Oct 2023 12:25:27 -0400 [thread overview]
Message-ID: <20231019-extinct-importer-8e3fce@meerkat> (raw)
In-Reply-To: <9879e427-5dd0-43ee-bacb-0b0b452ea348@sirena.org.uk>
On Thu, Oct 19, 2023 at 03:34:18PM +0100, Mark Brown wrote:
> > There's a third option -- instead of migrating the alsa-devel list, we can
> > migrate all activity to linux-sound@vger.kernel.org. It's an existing list
> > that currently sees about 5 messages a year (and most of them are cc'd to
> > alsa-devel anyway).
>
> That would definitely work well from my point of view.
Okay, since it doesn't really affect anything, I've reconfigured the patchwork
side of things to accept patches sent both to alsa-devel and linux-sound. If
you do want to go down the route of shifting everything towards linux-sound,
the next step (once everyone is in agreement), is to make the changes to
MAINTAINERS. You don't have to do all subsystems at once, you can start with
the SOUND subsystem to trial things out and then shift others if everything is
working correctly.
-K
next prev parent reply other threads:[~2023-10-19 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:25 Migrating this list to a different platform (take 2) Konstantin Ryabitsev
2023-10-19 13:14 ` Takashi Iwai
2023-10-19 14:01 ` Mark Brown
2023-10-19 13:57 ` Jaroslav Kysela
2023-10-19 14:32 ` Konstantin Ryabitsev
2023-10-19 14:34 ` Mark Brown
2023-10-19 16:25 ` Konstantin Ryabitsev [this message]
2023-10-20 7:00 ` Jaroslav Kysela
2023-10-20 7:44 ` Takashi Iwai
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=20231019-extinct-importer-8e3fce@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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