From: jjsullivan5196 <jjsullivan5196@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: phoc-0.4.2 calls-0.1.7 purism-chatty-0.1.15
Date: Sun, 13 Sep 2020 14:08:17 +0200 [thread overview]
Message-ID: <20200913120817.3ehkRc5S-36bi5adOytMACUVB1p9iwuZiTp4PJ9_xvg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24538@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
New comment by jjsullivan5196 on void-packages repository
https://github.com/void-linux/void-packages/pull/24538#issuecomment-691663364
Comment:
@julio641742 I wanted to take a look packaging `alsa-ucm-conf` when I was doing the first PR, but it was already pretty fat so I didn't want to put anymore weight on it. I can look into making sure the audio config is correct for the kernel, I've messed around with the alsa config already. Also, the person maintaining the sunxi audio codecs is working on some improvements for audio quality in kernel 5.9, so there might be room to experiment with that.
Also I do have modem.rules in `pinephone-base`, but that version doesn't run the modem setup script. Seems like it would be a good idea to add that in a separate PR.
Good work so far!
next prev parent reply other threads:[~2020-09-13 12:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 20:46 [PR PATCH] New packages: phoc-0.4.2 calls-0.1.7 purism-chatty--0.1.15 julio641742
2020-08-29 22:12 ` [PR REVIEW] " fosslinux
2020-08-29 22:12 ` fosslinux
2020-08-30 0:21 ` [PR PATCH] [Updated] " julio641742
2020-08-30 1:36 ` julio641742
2020-08-30 3:47 ` New packages: phoc-0.4.2 calls-0.1.7 purism-chatty-0.1.15 julio641742
2020-08-30 3:56 ` [PR REVIEW] " fosslinux
2020-08-30 3:56 ` fosslinux
2020-08-30 4:08 ` ericonr
2020-08-30 4:10 ` ericonr
2020-08-30 17:10 ` PaperMountainStudio
2020-08-31 0:27 ` [PR PATCH] [Updated] " julio641742
2020-08-31 0:32 ` julio641742
2020-08-31 0:35 ` [PR REVIEW] " julio641742
2020-08-31 0:39 ` [PR PATCH] [Updated] " julio641742
2020-08-31 0:41 ` julio641742
2020-08-31 1:06 ` [PR REVIEW] " ericonr
2020-09-12 18:00 ` [PR PATCH] [Updated] " julio641742
2020-09-12 18:19 ` julio641742
2020-09-12 18:46 ` julio641742
2020-09-12 18:52 ` julio641742
2020-09-12 21:46 ` [PR PATCH] [Updated] " julio641742
2020-09-12 22:08 ` julio641742
2020-09-12 22:23 ` julio641742
2020-09-12 22:32 ` julio641742
2020-09-12 23:17 ` julio641742
2020-09-13 5:35 ` [PR PATCH] [Updated] " julio641742
2020-09-13 5:53 ` julio641742
2020-09-13 7:42 ` julio641742
2020-09-13 12:08 ` jjsullivan5196
2020-09-13 12:08 ` jjsullivan5196 [this message]
2020-09-19 8:24 ` [PR PATCH] [Updated] " julio641742
2020-09-20 2:14 ` julio641742
2020-09-20 4:57 ` julio641742
2020-09-21 11:11 ` jjsullivan5196
2020-09-21 11:11 ` jjsullivan5196
2020-09-21 11:12 ` jjsullivan5196
2020-09-23 21:47 ` [PR PATCH] [Updated] " julio641742
2020-09-23 21:49 ` julio641742
2020-09-25 9:23 ` jjsullivan5196
2020-10-02 21:44 ` Frick-David
2021-02-27 14:20 ` jcgruenhage
2021-02-28 10:36 ` jcgruenhage
2021-02-28 20:05 ` jcgruenhage
2021-02-28 21:32 ` jcgruenhage
2022-04-19 2:12 ` github-actions
2022-05-03 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20200913120817.3ehkRc5S-36bi5adOytMACUVB1p9iwuZiTp4PJ9_xvg@z \
--to=jjsullivan5196@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).