From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.28
Date: Thu, 20 May 2021 20:29:12 +0200 [thread overview]
Message-ID: <20210520182912.WnsKMAIZ1AJSXFHIXQN0t9ngcWav6h2Ast1yXqUtGHU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31012@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/pull/31012#issuecomment-845363512
Comment:
of course the commit that fixes the `demonic.conf` bug has a cursed hash
next prev parent reply other threads:[~2021-05-20 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 11:26 [PR PATCH] " st3r4g
2021-05-20 18:25 ` [PR PATCH] [Updated] " st3r4g
2021-05-20 18:29 ` st3r4g [this message]
2021-05-21 0:05 ` ericonr
2021-05-21 7:39 ` [PR PATCH] [Updated] " st3r4g
2021-05-21 19:02 ` [PR PATCH] [Merged]: " ericonr
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=20210520182912.WnsKMAIZ1AJSXFHIXQN0t9ngcWav6h2Ast1yXqUtGHU@z \
--to=st3r4g@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).