From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tbb: update to 2021.5.0; update reverse dependencies
Date: Mon, 17 Jan 2022 07:53:10 +0100 [thread overview]
Message-ID: <20220117065310.zgx7FHcgObzK4nKToglBOIyA3970ya-S6pMgk6JQXVw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35077@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/35077#issuecomment-1014194490
Comment:
Because SuiteSparse took about an hour to build locally for me, the current plan is to test all of the dependent packages listed in the first comment on their own, see if they work in CI, and then push all of them at the end while skipping CI.
next prev parent reply other threads:[~2022-01-17 6:53 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 1:21 [PR PATCH] " cinerea0
2022-01-16 3:35 ` [PR PATCH] [Updated] " cinerea0
2022-01-16 4:03 ` cinerea0
2022-01-16 5:36 ` [PR PATCH] [Closed]: " cinerea0
2022-01-16 6:22 ` [PR PATCH] [Updated] " cinerea0
2022-01-16 7:00 ` cinerea0
2022-01-16 7:45 ` cinerea0
2022-01-16 15:16 ` notthewave
2022-01-16 15:19 ` notthewave
2022-01-16 15:42 ` notthewave
2022-01-16 15:42 ` notthewave
2022-01-16 15:43 ` notthewave
2022-01-16 15:51 ` notthewave
2022-01-16 15:52 ` notthewave
2022-01-16 15:52 ` notthewave
2022-01-16 18:41 ` [PR REVIEW] " ericonr
2022-01-16 18:41 ` ericonr
2022-01-16 18:41 ` ericonr
2022-01-16 23:42 ` cinerea0
2022-01-17 1:35 ` [PR PATCH] [Updated] " cinerea0
2022-01-17 3:17 ` cinerea0
2022-01-17 4:37 ` cinerea0
2022-01-17 5:06 ` cinerea0
2022-01-17 6:49 ` cinerea0
2022-01-17 6:53 ` cinerea0 [this message]
2022-01-17 16:03 ` cinerea0
2022-01-17 17:41 ` cinerea0
2022-01-17 19:00 ` cinerea0
2022-01-17 19:57 ` cinerea0
2022-01-19 20:53 ` cinerea0
2022-01-19 23:57 ` cinerea0
2022-01-20 15:45 ` cinerea0
2022-01-20 17:58 ` cinerea0
2022-01-20 18:27 ` cinerea0
2022-01-20 19:27 ` cinerea0
2022-01-20 21:20 ` cinerea0
2022-01-20 21:37 ` cinerea0
2022-01-20 22:20 ` cinerea0
2022-01-20 22:43 ` cinerea0
2022-01-20 23:49 ` [PR PATCH] [Updated] " cinerea0
2022-01-21 0:51 ` cinerea0
2022-01-21 1:23 ` cinerea0
2022-01-21 2:59 ` cinerea0
2022-01-21 3:55 ` cinerea0
2022-01-21 4:19 ` [PR PATCH] [Updated] " cinerea0
2022-01-21 5:49 ` cinerea0
2022-01-21 16:55 ` cinerea0
2022-01-24 17:09 ` cinerea0
2022-01-24 20:48 ` cinerea0
2022-01-24 22:03 ` cinerea0
2022-01-25 2:51 ` cinerea0
2022-01-25 4:23 ` [PR PATCH] [Updated] [ci skip] " cinerea0
2022-01-28 0:23 ` cinerea0
2022-01-28 6:27 ` [PR PATCH] [Closed]: " ericonr
2022-01-31 20:29 ` notthewave
2022-01-31 20:52 ` Duncaen
2022-01-31 23:57 ` paper42
2022-02-01 0:01 ` Duncaen
2022-02-01 0:07 ` Duncaen
2022-02-01 0:07 ` Duncaen
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=20220117065310.zgx7FHcgObzK4nKToglBOIyA3970ya-S6pMgk6JQXVw@z \
--to=cinerea0@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).