Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: calls + deps (callaudiod + feedbackd)
Date: Sat, 19 Nov 2022 12:23:34 +0100	[thread overview]
Message-ID: <20221119112334.VUswYUyPly8M8lvpiHZ202I3aMcHm4aJU49tN45U0-4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29138@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

New comment by jcgruenhage on void-packages repository

https://github.com/void-linux/void-packages/pull/29138#issuecomment-1320863335

Comment:
I'll try to take a look at this later today when I'm back at home and have access to my pinephone again. Would it make sense to merge those applications already even if the remaining stack for making calls isn't necessarily all there and tested already?

  parent reply	other threads:[~2022-11-19 11:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 21:27 [PR PATCH] " jcgruenhage
2021-02-28 22:42 ` [PR PATCH] [Updated] " jcgruenhage
2021-02-28 22:47 ` jcgruenhage
2021-02-28 22:49 ` jcgruenhage
2022-05-05  2:09 ` github-actions
2022-05-07 16:06 ` Piraty
2022-05-07 17:23 ` JamiKettunen
2022-05-07 17:23 ` JamiKettunen
2022-05-07 17:27 ` JamiKettunen
2022-05-10 19:02 ` jcgruenhage
2022-05-10 20:15 ` JamiKettunen
2022-05-10 20:16 ` JamiKettunen
2022-05-11 22:41 ` Piraty
2022-08-10  2:09 ` github-actions
2022-08-17  7:40 ` jcgruenhage
2022-11-17  2:10 ` github-actions
2022-11-18 19:16 ` Piraty
2022-11-19 11:23 ` jcgruenhage [this message]
2022-11-22 23:06 ` jcgruenhage
2022-11-24 14:45 ` jcgruenhage
2023-01-14 21:18 ` jcgruenhage
2023-01-14 23:28 ` JamiKettunen
2023-01-14 23:29 ` JamiKettunen
2023-01-15  2:02 ` jcgruenhage
2023-04-16  1:56 ` github-actions
2023-05-01  1:53 ` [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=20221119112334.VUswYUyPly8M8lvpiHZ202I3aMcHm4aJU49tN45U0-4@z \
    --to=jcgruenhage@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).