Hi Scott,
Scott Cheloha wrote on Sat, Dec 10, 2022 at 09:25:48AM -0600:
> Sure, I will keep the ERRORS section.
> I think the current phrasing in ERRORS is odd, though.
> "may set the global variable..." is what we normally say here, but it
> isn't a "may" in this case, it's an "always".
I
Updated patch looks good to me.
- todd
Sorry for the delay.
On Thu, Nov 10, 2022 at 08:19:51PM +0100, Ingo Schwarze wrote:
> Hi Scott,
>
> thanks for repeatedly working on time-related library documentation. :-)
>
> Unless noted otherwise, i agree with Todd's comments.
>
> Todd C. Miller wrote on Wed, Nov 09, 2022 at 10:31:15AM
Hi Scott,
thanks for repeatedly working on time-related library documentation. :-)
Unless noted otherwise, i agree with Todd's comments.
Todd C. Miller wrote on Wed, Nov 09, 2022 at 10:31:15AM -0700:
> On Wed, 09 Nov 2022 16:47:22 +, Scott Cheloha wrote:
>> RETURN VALUES
>>
>> - Pull
On Wed, 09 Nov 2022 16:47:22 +, Scott Cheloha wrote:
> I think this could use some sprucing.
>
> NAME
>
> - "stop until signal" -> "wait for a signal"
>
> Feels more natural to me.
OK
> DESCRIPTION
>
> - It's "the calling thread" that blocks, not "a process".
>
> - Nothing is "forced".
>
I think this could use some sprucing.
NAME
- "stop until signal" -> "wait for a signal"
Feels more natural to me.
DESCRIPTION
- It's "the calling thread" that blocks, not "a process".
- Nothing is "forced".
- It "blocks", it doesn't "pause". Saying pause(3) "pauses"
is too circular.
-
