From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.70
Date: Wed, 17 May 2023 20:17:55 +0200 [thread overview]
Message-ID: <20230517181755.-6jhJhY9a-wK5sepoAXVeOOMHU0BHP4XcwZWk5gHp6Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43574@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/43574#issuecomment-1551856117
Comment:
I agree that the best choice at this point is to drop p-m-s. The install message has been around for 4 package updates and almost 5 months, so it's not like people haven't been given warning. *There absolutely will be people whose setups break with this*, but I don't think anything besides a breakage would get them to change at this point.
I'm temporarily marking this as a draft while I test the new 0.3.71 release. I'd be happy to include the changes from the above-linked PR in this one if that would be the best way forward.
next prev parent reply other threads:[~2023-05-17 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 17:35 [PR PATCH] " cinerea0
2023-04-22 17:49 ` cinerea0
2023-05-06 1:53 ` ahesford
2023-05-06 1:54 ` ahesford
2023-05-06 3:04 ` oreo639
2023-05-06 3:05 ` oreo639
2023-05-06 3:07 ` oreo639
2023-05-06 3:47 ` ahesford
2023-05-15 21:49 ` marmeladema
2023-05-17 18:17 ` cinerea0 [this message]
2023-05-18 13:28 ` ahesford
2023-05-20 2:38 ` [PR PATCH] [Updated] " cinerea0
2023-05-24 17:10 ` [PR PATCH] [Closed]: pipewire: update to 0.3.71, drop pipewire-media-session ahesford
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=20230517181755.-6jhJhY9a-wK5sepoAXVeOOMHU0BHP4XcwZWk5gHp6Q@z \
--to=cinerea0@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).