From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] pipewire: update, rename pipewire-utils, add new meta to pull in wireplumber
Date: Wed, 25 Jan 2023 22:32:16 +0100 [thread overview]
Message-ID: <20230125213216.E8YlMB7l7BuPLf_TmZIHHFfhHgI1CFzOTcaxqQP_sYk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41868@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41868#issuecomment-1404250353
Comment:
I would prefer to avoid the renaming scheme if possible. Would the implementation of the alternate proposal make intuitive sense if you generally understand xbps templates?
next prev parent reply other threads:[~2023-01-25 21:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 16:31 [PR PATCH] " ahesford
2023-01-25 16:49 ` [PR PATCH] [Updated] " ahesford
2023-01-25 16:51 ` ahesford
2023-01-25 21:32 ` cinerea0 [this message]
2023-01-26 2:48 ` cinerea0
2023-01-26 2:49 ` [PR PATCH] [Updated] " ahesford
2023-01-26 2:53 ` ahesford
2023-01-26 2:56 ` ahesford
2023-01-26 14:06 ` [PR PATCH] [Updated] " ahesford
2023-01-26 14:08 ` ahesford
2023-01-26 14:08 ` ahesford
2023-01-28 14:35 ` [PR PATCH] [Updated] [RFC] pipewire: update, add virtual session manager to pull in wireplumber without build cycle ahesford
2023-01-30 20:51 ` ahesford
2023-02-04 2:35 ` ahesford
2023-02-04 12:17 ` ahesford
2023-02-04 19:01 ` ahesford
2023-05-06 1:48 ` github-actions
2023-05-06 1:55 ` ahesford
2023-05-24 17:10 ` ahesford
2023-05-24 17:10 ` [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=20230125213216.E8YlMB7l7BuPLf_TmZIHHFfhHgI1CFzOTcaxqQP_sYk@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).