Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [rfc] native aarch64 builders
Date: Tue, 13 Jun 2023 23:02:11 +0200	[thread overview]
Message-ID: <20230613210211.iwkDHHfZUHsQJQghx6TQWHNk5qhlIXUWfdgJv05ki9g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40980@inbox.vuxu.org>

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/40980#issuecomment-1590021511

Comment:
This is not really an RFC and I fail to see the point of this, yes native build servers would be better, everyone agrees. We don't ask for donations and can't take donations, keeping issues like this open that looks like a public request for donations is misleading.


  parent reply	other threads:[~2023-06-13 21:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 16:19 [ISSUE] " dkwo
2022-12-12 20:14 ` Eloitor
2022-12-12 20:28 ` classabbyamp
2022-12-12 20:53 ` dkwo
2022-12-12 21:54 ` Eloitor
2022-12-14 14:05 ` leahneukirchen
2022-12-14 14:06 ` tornaria
2022-12-14 14:07 ` leahneukirchen
2022-12-14 14:45 ` dkwo
2022-12-14 14:46 ` dkwo
2022-12-14 16:11 ` leahneukirchen
2022-12-14 16:28 ` dkwo
2022-12-14 17:30 ` paper42
2022-12-15 23:00 ` leahneukirchen
2022-12-15 23:28 ` vincele
2023-01-07 15:19 ` dkwo
2023-02-10  5:29 ` BikyAlex
2023-02-10  5:29 ` BikyAlex
2023-04-12  8:43 ` vincele
2023-06-13 20:47 ` dkwo
2023-06-13 20:49 ` Duncaen
2023-06-13 20:50 ` Duncaen
2023-06-13 21:01 ` [ISSUE] [CLOSED] " Duncaen
2023-06-13 21:01 ` Duncaen
2023-06-13 21:02 ` Duncaen [this message]
2023-07-12 16:36 ` dkwo
2024-02-16 15:20 ` dkwo
2024-02-16 15:31 ` BikyAlex
2024-02-16 15:40 ` dkwo

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=20230613210211.iwkDHHfZUHsQJQghx6TQWHNk5qhlIXUWfdgJv05ki9g@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).