From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.65
Date: Sat, 28 Jan 2023 15:39:32 +0100 [thread overview]
Message-ID: <20230128143932.uaFfueWBwUoE2EYFa_XOR1XIttn1PQKTUiN9aCnaGtc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41846@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/41846#issuecomment-1407412278
Comment:
There has been a lot of bikeshedding around pipewire, and I suspect there will continue to be more as we iron out the wrinkles in wireplumber documentation. None of that changes the fact that pipewire-media-session will soon become unmaintainable and we should drop it eventually. People should have the maximum possible notice that this will happen, even if the docs aren't quite ready.
prev parent reply other threads:[~2023-01-28 14:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 19:40 [PR PATCH] pipewire: update to 0.3.64 cinerea0
2023-01-24 19:47 ` cinerea0
2023-01-24 19:47 ` oreo639
2023-01-24 19:47 ` oreo639
2023-01-24 20:18 ` cinerea0
2023-01-24 20:39 ` [PR PATCH] [Updated] " cinerea0
2023-01-25 14:54 ` ahesford
2023-01-25 21:46 ` [PR PATCH] [Updated] " cinerea0
2023-01-25 21:48 ` cinerea0
2023-01-25 21:54 ` cinerea0
2023-01-25 22:00 ` [PR REVIEW] " ahesford
2023-01-26 2:14 ` [PR PATCH] [Updated] " cinerea0
2023-01-26 2:15 ` [PR REVIEW] " cinerea0
2023-01-26 7:22 ` paper42
2023-01-26 11:03 ` paper42
2023-01-26 15:11 ` ahesford
2023-01-27 18:00 ` [PR PATCH] [Updated] " cinerea0
2023-01-27 18:02 ` cinerea0
2023-01-27 18:04 ` [PR PATCH] [Updated] " cinerea0
2023-01-27 18:23 ` cinerea0
2023-01-27 18:34 ` ahesford
2023-01-27 22:14 ` [PR PATCH] [Updated] " cinerea0
2023-01-27 23:29 ` pipewire: update to 0.3.65 cinerea0
2023-01-28 11:12 ` ardadem
2023-01-28 14:33 ` [PR PATCH] [Closed]: " ahesford
2023-01-28 14:39 ` ahesford [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=20230128143932.uaFfueWBwUoE2EYFa_XOR1XIttn1PQKTUiN9aCnaGtc@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).