From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chromium: enable pipewire webrtc backend
Date: Sat, 23 May 2020 17:46:56 +0200 [thread overview]
Message-ID: <20200523154656.b4stjH8Hwrg5N8-Ih7F7FtUxsZk60ClAzZIToFnE03I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22222@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
New comment by ifreund on void-packages repository
https://github.com/void-linux/void-packages/pull/22222#issuecomment-633080013
Comment:
On looking into this further it seems like it would make more sense to first update pipewire to 0.3, then create a `libpipewire-0.2` package and enable it in chrome in a follow up PR.
next prev parent reply other threads:[~2020-05-23 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 9:34 [PR PATCH] " ifreund
2020-05-23 9:51 ` [PR PATCH] [Updated] " ifreund
2020-05-23 15:46 ` ifreund [this message]
2020-05-23 15:46 ` [PR PATCH] [Closed]: " ifreund
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=20200523154656.b4stjH8Hwrg5N8-Ih7F7FtUxsZk60ClAzZIToFnE03I@z \
--to=ifreund@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).