From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] blender: update to 2.90.1.
Date: Wed, 14 Oct 2020 20:55:47 +0200 [thread overview]
Message-ID: <20201014185547.EYOut4bCPKrPcGknHEdwNpvVzQFnzN57AFJuRARzezs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25547@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
New review comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/25547#discussion_r504902148
Comment:
I pulled your `openimageio` bump and see what you mean about `luxmark` and `luxrays`. For the moment I will defer addressing this issue because the upstream sources for `luxmark` and `luxrays` seem to have moved and it's not clear to me where the new repos are. (I see a `luxmark` repo on GitHub, but `luxrays` seems to have disappeared.)
Because `blender` is currently broken with system Python, I'm going to merge this as-is and let somebody else propose a solution for moving to a new `openimageio` in the future.
next prev parent reply other threads:[~2020-10-14 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 18:43 [PR PATCH] " ahesford
2020-10-12 20:12 ` [PR PATCH] [Updated] " ahesford
2020-10-12 21:12 ` martnnw
2020-10-13 19:33 ` [PR PATCH] [Updated] " ahesford
2020-10-13 19:34 ` ahesford
2020-10-13 19:39 ` ahesford
2020-10-14 1:49 ` ericonr
2020-10-14 14:19 ` [PR PATCH] [Updated] " ahesford
2020-10-14 14:55 ` [PR REVIEW] " mvf
2020-10-14 14:56 ` mvf
2020-10-14 18:55 ` ahesford [this message]
2020-10-14 19:17 ` [PR PATCH] [Closed]: " ahesford
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=20201014185547.EYOut4bCPKrPcGknHEdwNpvVzQFnzN57AFJuRARzezs@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).