From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nim: update to 1.6.0, fix non-x86_64/i686 packages, improve template
Date: Sat, 04 Dec 2021 05:27:16 +0100 [thread overview]
Message-ID: <20211204042716.ZtWg8u1mXNQajUM_GEEMZviRQbU-VOM4h9ERSwDdflk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34106@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/34106#issuecomment-985965090
Comment:
> But in the meanwhile, if this does end up working in CI, I would like to keep it that way and get this version bump merged. Then doing i686 builds properly can be a task for later.
FWIW i686 is built natively.
next prev parent reply other threads:[~2021-12-04 4:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 20:40 [PR PATCH] [RFC] nim: update to 1.6.0 EliteTK
2021-11-16 20:48 ` [PR PATCH] [Updated] " EliteTK
2021-11-16 21:20 ` EliteTK
2021-11-17 23:37 ` [PR PATCH] [Updated] " EliteTK
2021-11-17 23:45 ` EliteTK
2021-11-18 7:40 ` [PR PATCH] [Updated] " EliteTK
2021-11-18 9:24 ` EliteTK
2021-11-18 9:26 ` EliteTK
2021-11-18 19:18 ` EliteTK
2021-11-18 20:10 ` [PR PATCH] [Updated] " EliteTK
2021-11-18 20:12 ` nim: update to 1.6.0, fix non-x86_64/i686 packages, improve template EliteTK
2021-11-18 20:21 ` [PR PATCH] [Updated] " EliteTK
2021-11-19 23:07 ` EliteTK
2021-11-19 23:07 ` EliteTK
2021-11-19 23:13 ` EliteTK
2021-11-19 23:21 ` EliteTK
2021-11-19 23:25 ` EliteTK
2021-12-04 4:27 ` ericonr [this message]
2021-12-04 4:30 ` [PR PATCH] [Merged]: " ericonr
2021-12-04 4:30 ` 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=20211204042716.ZtWg8u1mXNQajUM_GEEMZviRQbU-VOM4h9ERSwDdflk@z \
--to=ericonr@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).