This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v4 11/12] Update NEWS for new _clockwait and _clocklock functions
On 18/06/2019 13:33, Mike Crowe wrote:
> * NEWS: Mention recently-added pthread_cond_clockwait,
> pthread_mutex_clocklock, pthread_rwlock_clockrdlock,
> pthread_rwlock_clockwrlock and sem_clockwait functions.
LGTM, I will commit this for you.
> ---
> ChangeLog | 6 ++++++
> NEWS | 9 +++++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/ChangeLog b/ChangeLog
> index a213eb1..984275c 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,9 @@
> +2019-05-27 Mike Crowe <mac@mcrowe.com>
> +
> + * NEWS: Mention recently-added pthread_cond_clockwait,
> + pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock and
> + sem_clockwait functions.
> +
> 2019-05-31 Mike Crowe <mac@mcrowe.com>
>
> nptl: Add POSIX-proposed pthread_mutex_clocklock function that
> diff --git a/NEWS b/NEWS
> index 8a2fece..653a69d 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -34,6 +34,15 @@ Major new features:
> pointer subtraction within the allocated object, where results might
> overflow the ptrdiff_t type.
>
> +* Add new POSIX-proposed pthread_cond_clockwait, pthread_mutex_clocklock,
> + pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock and sem_clockwait
> + functions. These behave similarly to their "timed" equivalents, but also
> + accept a clockid_t parameter to determine which clock their timeout should
> + be measured against. All functions allow waiting against CLOCK_MONOTONIC
> + and CLOCK_REALTIME. The decision of which clock to be used is made at the
> + time of the wait (unlike with pthread_condattr_setclock, which requires
> + the clock choice at initialization time.)
> +
Two spaces after period and ) after period (I will fix it for you).
> Deprecated and removed features, and other changes affecting compatibility:
>
> * The functions clock_gettime, clock_getres, clock_settime,
>