From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.70
Date: Sat, 06 May 2023 05:04:50 +0200 [thread overview]
Message-ID: <20230506030450.Yp3S3HG8Gv2SUSVDAvkSAFD-nK6ZDrX4w0p8Gk8MK9E@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: 652 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/43574#issuecomment-1537025378
Comment:
> we sure as hell shouldn't start patching it, so the choice is between leaving it alone or dropping it altogether.
It isn't about adding a new patch, it is about updating the existing path for this:
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/27bc60aeab83a91d4eae3be14f6eff4f67552d02
See here in the diff (i.e. should the `@sm_comment@` be there or not):
`@sm_comment@ condition = [ { exec.session-manager = null } { exec.session-manager = true } ]`
Unless I am misunderstanding you?
next prev parent reply other threads:[~2023-05-06 3:04 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 [this message]
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
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=20230506030450.Yp3S3HG8Gv2SUSVDAvkSAFD-nK6ZDrX4w0p8Gk8MK9E@z \
--to=oreo639@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).