FWIW, my main impetus for pointing out PR #155 is that it's the smallest 
possible patch to make Windows successfully compile.

I don't mean to judge other's contributions one way or another, only trying to 
find the quickest possible way to get the build back on line - much better to 
start integrations from something that works and tests okay, is what I was 
thinking.

Also I should point out that I don't hold write access to the repo, I only 
offer opinions based on having spent years maintaining portions of the code, 
especially the Windows build, while I was at ILM, in the hope that those 
opinions are helpful.

- Nick

________________________________________
From: Kevin Wheatley <kevin.j.wheat...@gmail.com>
Sent: Monday, April 25, 2016 2:16 AM
To: Nick Porcino
Cc: Ed Hanway; Karl Rasche; openexr-devel@nongnu.org
Subject: Re: [Openexr-devel] Speaking of PRs...

FWIW, my build is based on

https://github.com/KevinJW/openexr/tree/develop

which also includes the Foundry's Nuke patch, plus a few tidy ups,
can't remember if I sent in pull requests for everything, though I
think I did.

Kevin

_______________________________________________
Openexr-devel mailing list
Openexr-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/openexr-devel

Reply via email to