From: Animeshz <Animeshz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] wireplumber: Add runit service
Date: Wed, 30 Mar 2022 16:29:26 +0200 [thread overview]
Message-ID: <20220330142926.e2cnOF5Dr0WRFwj9aDi7Lin75XDmcVJTMO2GAAnr1G4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36416@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
New review comment by Animeshz on void-packages repository
https://github.com/void-linux/void-packages/pull/36416#discussion_r838614429
Comment:
I'm not too sure why its necessary, I just created an upstream issue [wireplumber#237](https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/237) for the enquiry.
next prev parent reply other threads:[~2022-03-30 14:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:42 [PR PATCH] Add wireplumber " Animeshz
2022-03-30 10:43 ` [PR PATCH] [Updated] " Animeshz
2022-03-30 11:26 ` [PR REVIEW] wireplumber: Add " ahesford
2022-03-30 11:26 ` ahesford
2022-03-30 11:26 ` ahesford
2022-03-30 11:50 ` Animeshz
2022-03-30 11:52 ` Animeshz
2022-03-30 11:52 ` Animeshz
2022-03-30 11:55 ` Animeshz
2022-03-30 11:55 ` Animeshz
2022-03-30 12:03 ` Animeshz
2022-03-30 12:03 ` Animeshz
2022-03-30 12:04 ` Animeshz
2022-03-30 12:05 ` Animeshz
2022-03-30 12:10 ` Animeshz
2022-03-30 12:30 ` ahesford
2022-03-30 12:33 ` ahesford
2022-03-30 12:37 ` ahesford
2022-03-30 12:40 ` ahesford
2022-03-30 12:53 ` Animeshz
2022-03-30 12:53 ` Animeshz
2022-03-30 13:09 ` [PR PATCH] [Updated] " Animeshz
2022-03-30 14:29 ` Animeshz [this message]
2022-03-30 14:31 ` Animeshz
2022-03-30 17:36 ` [PR REVIEW] " subnut
2022-03-30 17:40 ` subnut
2022-03-30 18:13 ` Animeshz
2022-03-30 18:18 ` Animeshz
2022-03-30 18:25 ` Animeshz
2022-03-30 18:28 ` Animeshz
2022-03-31 2:13 ` [PR PATCH] [Closed]: " 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=20220330142926.e2cnOF5Dr0WRFwj9aDi7Lin75XDmcVJTMO2GAAnr1G4@z \
--to=animeshz@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).