From: Snowmean <Snowmean@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: sview-20.08
Date: Thu, 01 Oct 2020 14:45:35 +0200 [thread overview]
Message-ID: <20201001124535.Sgh-s3EVUJbUPWU3GEr9WSHv8X4A-n2dZ3i_H3OFwAU@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: 422 bytes --]
New review comment by Snowmean on void-packages repository
https://github.com/void-linux/void-packages/pull/25204#discussion_r498215326
Comment:
I'm finding my experience with `./xbps-src -a <arch> pkg sview` quite different from what I see in TravisCI. Am I doing something wrong? Is there a way to implement the same build environment as you are using for TravisCI? I'd like to avoid pushing bunch of testing commits.
next prev parent reply other threads:[~2020-10-01 12:45 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 [this message]
2020-10-01 15:07 ` ericonr
2020-10-02 3:16 ` Snowmean
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=20201001124535.Sgh-s3EVUJbUPWU3GEr9WSHv8X4A-n2dZ3i_H3OFwAU@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).