G. Branden Robinson wrote:
> References:
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/include/sys/types.h

An archaeologically interesting archive :)

> ---
>  doc/gnulib-readme.texi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/gnulib-readme.texi b/doc/gnulib-readme.texi
> index 3d2d09fefb..aa1b1524a2 100644
> --- a/doc/gnulib-readme.texi
> +++ b/doc/gnulib-readme.texi
> @@ -332,8 +332,8 @@
>  @code{<locale.h>}, @code{<signal.h>}, @code{<stdio.h>},
>  @code{<stdlib.h>}, @code{<string.h>}, and @code{<time.h>}.  Similarly,
>  many modules include @code{<sys/types.h>} even though it's not
> -in the C standard; that's OK since @code{<sys/types.h>} has been around 
> nearly
> -forever.
> +in the C standard; that's OK since @code{<sys/types.h>} has been around
> +since Seventh Edition Unix (1979).
>  
>  Even if the include files exist, they may not conform to the C standard.
>  However, GCC has a @command{fixincludes} script that attempts to fix most
> 

Thanks, applied with a change: I put the reference into a comment
instead of the commit message.
https://gitweb.git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cd3725d66cfb18e2742686d6cf010c5bda9b60db

Bruno




Reply via email to