Re: Typo in memchr(3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[Resending to linux-man@xxxxxxxxxxxxxxx]

On Thu, Sep 8, 2011 at 6:07 PM, Michael Kerrisk <mtk.manpages@xxxxxxxxx> wrote:
> On Mon, Aug 15, 2011 at 9:39 AM, Johannes Laire <johannes@xxxxxxxx> wrote:
>> memchr(3)
>>> If the character c is not in the string s, then rawmemchr() may proceed to
>>> search beyond the end of the string, and the result is unspecified. The
>>> folowing call is a fast means of locating a string's terminating null byte:
>>
>> The word "folowing" needs a second "l". Also, "undefined" instead of
>> "unspecified" would be more in line with common C usage.
>
> Thanks. Fixed for man-pages-3.33.
>
> Cheers,
>
> Michael
>
>
> --
> Michael Kerrisk
> Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
> Author of "The Linux Programming Interface"; http://man7.org/tlpi/
>



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux