From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Updates to documentation
Date: Fri, 10 Jul 2020 01:24:43 +0200 [thread overview]
Message-ID: <20200709232443.ukRHA1ZkjXj6dD4dv2sknSAXUm68RrX3uOEPfm4OIAk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23475@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
New review comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/23475#discussion_r452542313
Comment:
Maybe something like:
> Pull requests are automatically submitted for Continuous Integration (CI) testing to ensure packages build on various architectures and C libraries. Packages that take longer than 50 minutes to build (for example, Firefox or the Linux kernel) will fail CI and should include `[ci skip]` in the commit message of the last commit in the PR to avoid wasting CI builder time. Use your best judgment on build times based on your local building experience. If you skip CI when submitting a PR, please locally build for a variety of architectures with glibc as well as musl and note your local results in PR comments.
next prev parent reply other threads:[~2020-07-09 23:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 19:45 [PR PATCH] " ericonr
2020-07-09 23:24 ` ahesford [this message]
2020-07-09 23:43 ` [PR REVIEW] " ericonr
2020-07-10 3:46 ` ahesford
2020-07-10 4:10 ` [PR PATCH] [Updated] " ericonr
2020-07-10 4:10 ` [PR REVIEW] " ericonr
2020-07-11 19:44 ` Chocimier
2020-07-11 19:44 ` Chocimier
2020-07-11 19:44 ` Chocimier
2020-07-11 20:08 ` ahesford
2020-07-11 22:34 ` ericonr
2020-07-12 3:37 ` ahesford
2020-07-12 13:58 ` [PR PATCH] [Updated] " ericonr
2020-07-12 13:58 ` ericonr
2020-07-13 16:21 ` [PR PATCH] [Merged]: " Chocimier
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=20200709232443.ukRHA1ZkjXj6dD4dv2sknSAXUm68RrX3uOEPfm4OIAk@z \
--to=ahesford@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).