On Wed, Feb 27, 2019 at 5:06 PM William A Rowe Jr <wr...@rowe-clan.net>

> With several new features added to the 1.7 branch, the fixes to the
> Netware locking we had deferred, and the proposed correction of
> SIGUSR2, I'm wondering what we see as remaining obstacles.

These two appear to be in good shape. Who has reviewed the addition
and further patches to the 64 bit portable atomics? Do we have a few
reviewers who agree these are good to lock down and publish?

I'd like to proceed with addressing the symlink vs. "other" reparse tag
> questions raised for Windows, and will make the time to get the current
> patch proposal and my type safety cleanups into trunk. PR 47630.
> I'm also interested in fixing SFU issues of the Ubuntu on Windows
> implementation with APR locking, and can dedicate a few hours
> this weekend to look at where those errors stand.

This weekend is looking good here for fixing the reparse tag questions
and further review of locking on the SFU Windows subsystem (by which
I mean, finally warmer, but much wetter and a good time to be indoors
in Chicagoland.)

Do we want to do something about de-prioritizing sysv semaphores
> on linux by default with the 1.7.0 release?

Comments? I know some distributors already hack around our default
autoconf locking mechanism choice on modern Linux.

I'd like to give this question a few more days, and finally lock down
our 1.7.0 candidate sometime later next week.

Reply via email to