Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: armcord-3.1.4
Date: Sat, 31 Dec 2022 21:13:43 +0100	[thread overview]
Message-ID: <20221231201343.cPvfRLeWO_FEKRylLoublb5M6FM3F5gp-u_c9kyu-14@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41385@inbox.vuxu.org>

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/pull/41385#issuecomment-1368275042

Comment:
How is that supposed to work, you are not building electron from source or use the system wide electron, where are the armv7l-musl binaries coming from?

  reply	other threads:[~2022-12-31 20:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 18:21 [PR PATCH] " Zoh-j02r
2022-12-31 20:13 ` Duncaen [this message]
2022-12-31 20:55 ` paper42
2023-01-01 15:55 ` [PR PATCH] [Updated] " Zoh-j02r
2023-01-01 16:07 ` Zoh-j02r
2023-01-01 16:23 ` Zoh-j02r
2023-01-01 18:59 ` [PR REVIEW] " Vendicated
2023-01-01 19:03 ` Vendicated
2023-01-03  1:06 ` [PR PATCH] [Updated] " Zoh-j02r
2023-01-03  1:08 ` Zoh-j02r
2023-01-03  1:13 ` Zoh-j02r
2023-01-03  1:14 ` Zoh-j02r
2023-01-03 18:21 ` Zoh-j02r
2023-01-03 18:27 ` [PR PATCH] [Updated] " Zoh-j02r
2023-01-03 18:28 ` Zoh-j02r
2023-01-03 18:32 ` Zoh-j02r
2023-01-07 17:40 ` yurifuko
2023-01-08  0:49 ` [PR PATCH] [Updated] " Zoh-j02r
2023-01-08  1:10 ` Zoh-j02r
2023-01-08  1:12 ` Zoh-j02r
2023-01-08  9:46 ` paper42
2023-01-08  9:46 ` [PR REVIEW] " paper42
2023-01-08 13:49 ` Zoh-j02r
2023-03-08 23:22 ` [PR PATCH] [Updated] " Zoh-j02r
2023-03-20  7:54 ` paper42
2023-03-20 11:13 ` Zoh-j02r
2023-03-22 23:42 ` paper42
2023-03-22 23:42 ` [PR PATCH] [Closed]: " paper42

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=20221231201343.cPvfRLeWO_FEKRylLoublb5M6FM3F5gp-u_c9kyu-14@z \
    --to=duncaen@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).