On 2025-03-04T20:00:13-0800, Hal Murray via devel wrote:
> Do we want to get a release out now or continue fixing/tweaking things?
The Internet recommends releasing early and often to improve engagement; we do
neither.
===
On 2025-03-04T20:55:06-0800, Matt Selsky via devel wrote:
> - Are there
Thanks. Your comments seem good to me.
Does new waf run on python 2.7?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
On 2025-03-04 23:37, Hal Murray via devel wrote:
matthew.sel...@twosigma.com said:
I sounds like we would want a release out before we start mucking with
threads given that your review of the code shows a lot of potential
complexity.
It's not so much the complexity as the time. We've been ta
matthew.sel...@twosigma.com said:
> I sounds like we would want a release out before we start mucking with
> threads given that your review of the code shows a lot of potential
> complexity.
It's not so much the complexity as the time. We've been talking about a
release for a long time. How
On Tue, Mar 04, 2025 at 08:00:13PM -0800, Hal Murray via devel wrote:
> Do we want to get a release out now or continue fixing/tweaking things?
I sounds like we would want a release out before we start mucking with threads
given that your review of the code shows a lot of potential complexity.
I've been trying to cleanup the thread priorities. So far, all I have is
a sore head.
The root of the problem is that we are creating the threads after dropping
root. You might think that it would be OK to reduce your priority, but it
doesn't work that way.
pthread_create() has
