From: Snowmean <Snowmean@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: sview-20.08
Date: Fri, 02 Oct 2020 05:16:54 +0200 [thread overview]
Message-ID: <20201002031654.L-_QzH5WG3pBotTAOz5nOPCgLfk7__5LaxcFCj4eXD0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25204@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
New review comment by Snowmean on void-packages repository
https://github.com/void-linux/void-packages/pull/25204#discussion_r498603201
Comment:
For example i686 build is failing in chroot while passing compilation test in TravisCI, arm\aarch and mips compilations also fails quite differently to what Travis shows, however the template is the same across both, hence the question.
next prev parent reply other threads:[~2020-10-02 3:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 9:28 [PR PATCH] " Snowmean
2020-09-30 9:36 ` [PR PATCH] [Updated] " Snowmean
2020-09-30 9:42 ` Snowmean
2020-09-30 9:53 ` Snowmean
2020-09-30 18:08 ` [PR REVIEW] " Chocimier
2020-09-30 21:46 ` Snowmean
2020-10-01 1:02 ` ericonr
2020-10-01 1:29 ` [PR PATCH] [Updated] " Snowmean
2020-10-01 2:06 ` Snowmean
2020-10-01 2:16 ` [PR REVIEW] " Snowmean
2020-10-01 2:31 ` ericonr
2020-10-01 2:45 ` ericonr
2020-10-01 6:19 ` Chocimier
2020-10-01 6:27 ` Chocimier
2020-10-01 6:27 ` Chocimier
2020-10-01 6:27 ` Chocimier
2020-10-01 8:03 ` Snowmean
2020-10-01 8:04 ` Snowmean
2020-10-01 12:45 ` Snowmean
2020-10-01 15:07 ` ericonr
2020-10-02 3:16 ` Snowmean [this message]
2020-10-02 3:20 ` ericonr
2020-10-02 3:20 ` ericonr
2020-10-06 10:22 ` [PR PATCH] [Updated] " Snowmean
2020-12-20 1:56 ` ericonr
2021-07-20 20:30 ` [PR REVIEW] " ericonr
2021-07-20 20:30 ` ericonr
2021-07-20 20:30 ` ericonr
2022-04-20 2:14 ` github-actions
2022-05-04 2:15 ` [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=20201002031654.L-_QzH5WG3pBotTAOz5nOPCgLfk7__5LaxcFCj4eXD0@z \
--to=snowmean@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).