From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gitui: update to 0.10.1.
Date: Thu, 03 Sep 2020 16:51:40 +0200 [thread overview]
Message-ID: <20200903145140.mucyoILN1vg6vtrs_U1bsPqsK3slPFiLdgRFWqI8gO4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24547@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/24547#issuecomment-686541413
Comment:
> Please try to test building locally.
Isn't that what the CI is for?
For new packages, I always build them locally and test them in runtime, but compiling them for each version bump is a bit much with these rust packages as rust has quite long compilation times. If xbps-src had support for (global) compilation caches in rust builds, using sccache or something like that, it'd be okay, but like this it just eats up too much time.
next prev parent reply other threads:[~2020-09-03 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 12:24 [PR PATCH] gitui: update to 0.10.0 jcgruenhage
2020-09-03 11:53 ` [PR PATCH] [Updated] " jcgruenhage
2020-09-03 12:02 ` [PR REVIEW] gitui: update to 0.10.1 jcgruenhage
2020-09-03 12:10 ` jcgruenhage
2020-09-03 12:16 ` ericonr
2020-09-03 14:43 ` jcgruenhage
2020-09-03 14:48 ` jcgruenhage
2020-09-03 14:51 ` jcgruenhage [this message]
2020-09-03 14:53 ` Duncaen
2020-09-03 14:59 ` ericonr
2020-09-03 15:05 ` jcgruenhage
2020-09-03 15:10 ` ericonr
2020-09-03 15:10 ` jcgruenhage
2020-09-03 15:12 ` jcgruenhage
2020-09-03 16:25 ` jcgruenhage
2020-09-03 17:40 ` Duncaen
2020-10-24 10:41 ` [PR PATCH] [Updated] " jcgruenhage
2020-10-24 10:44 ` jcgruenhage
2020-10-24 11:26 ` jcgruenhage
2020-12-20 1:26 ` [PR PATCH] [Merged]: " 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=20200903145140.mucyoILN1vg6vtrs_U1bsPqsK3slPFiLdgRFWqI8gO4@z \
--to=jcgruenhage@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).