From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: crun: update to 1.4.2.
Date: Sat, 05 Feb 2022 13:54:24 +0100 [thread overview]
Message-ID: <20220205125424.vvZPpvlKL9MsILfzXwvIlq2xecKsMO7pqzZRhcDXhhI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35388@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
New comment by natrys on void-packages repository
https://github.com/void-linux/void-packages/pull/35388#issuecomment-1030619458
Comment:
@paper42 don't think that's semantically equivalent. If I remember, it was done like this mostly to stop tests from running in CI (they don't even work locally because of chroot), and probably because `ci-skip` wasn't a thing yet. So I would think equivalent would be `make_check=ci-skip` altogether, should I do that instead?
next prev parent reply other threads:[~2022-02-05 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:44 [PR PATCH] " natrys
2022-02-05 12:54 ` natrys [this message]
2022-02-05 14:34 ` paper42
2022-04-07 17:15 ` [PR PATCH] [Closed]: " leahneukirchen
2022-04-07 17:15 ` leahneukirchen
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=20220205125424.vvZPpvlKL9MsILfzXwvIlq2xecKsMO7pqzZRhcDXhhI@z \
--to=natrys@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).