From: Andreas Jaeger <aj@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Various manual fixes...
Date: Sat, 27 Oct 2007 16:31:00 -0000 [thread overview]
Message-ID: <87ve8so6y7.fsf@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 5857 bytes --]
Ok to commit the following fixes for the manual?
Andreas
2007-10-27 Andreas Jaeger <aj@suse.de>,
* manual/libc.texinfo: Update for version 2.8 and latest commits.
[BZ #4887]
* manual/startup.texi (Environment Access): Explain that putenv,
setenv, clearenv, and unsetenv are not thread safe.
Patch by Takashi Nishiie <t-nishiie@soft.fujitsu.com>.
* manual/process.texi (Executing a File): Fix xref usage.
* manual/startup.texi (Program Basics): Likewise.
* manual/stdio.texi (Variable Arguments Input): Likewise.
* manual/sysinfo.texi (Host Identification): Likewise.
* manual/syslog.texi (Overview of Syslog): Likewise.
* manual/time.texi (Processor And CPU Time): Likewise.
Patch by Karl Berry <karl@freefriends.org>.
* manual/texinfo.tex: Update to latest version.
[BZ #5180]
* manual/socket.texi (Listening): Fix typo of listen.
============================================================
Index: manual/socket.texi
--- manual/socket.texi 6 Jul 2001 06:55:18 -0000 1.70
+++ manual/socket.texi 27 Oct 2007 15:55:36 -0000
@@ -2070,7 +2070,7 @@ access to connect to the socket.
@comment sys/socket.h
@comment BSD
-@deftypefun int listen (int @var{socket}, unsigned int @var{n})
+@deftypefun int listen (int @var{socket}, int @var{n})
The @code{listen} function enables the socket @var{socket} to accept
connections, thus making it a server socket.
--- manual/process.texi 2001-05-21 18:19:34.000000000 +0200
+++ manual/process.texi 2007-10-07 20:43:10.000000000 +0200
@@ -279,3 +279,3 @@ process execute a new program after it h
To see the effects of @code{exec} from the point of view of the called
-program, @xref{Program Basics}.
+program, see @ref{Program Basics}.
--- manual/startup.texi 2006-11-10 22:10:22.000000000 +0100
+++ manual/startup.texi 2007-10-07 20:43:10.000000000 +0200
@@ -33,3 +33,3 @@ A program starts another program with th
This chapter looks at program startup from the execee's point of view. To
-see the event from the execor's point of view, @xref{Executing a File}.
+see the event from the execor's point of view, see @ref{Executing a File}.
--- manual/stdio.texi 2006-11-10 22:10:22.000000000 +0100
+++ manual/stdio.texi 2007-10-07 20:43:10.000000000 +0200
@@ -3910,3 +3910,3 @@ can check the number and types of argume
function, and warn you when they do not match the format string.
-For details, @xref{Function Attributes, , Declaring Attributes of Functions,
+For details, see @ref{Function Attributes, , Declaring Attributes of Functions,
gcc.info, Using GNU CC}.
--- manual/sysinfo.texi 2006-11-10 22:10:22.000000000 +0100
+++ manual/sysinfo.texi 2007-10-07 20:43:10.000000000 +0200
@@ -80,3 +80,3 @@ In some contexts, the host name is calle
-For more information on DNS host naming, @xref{Host Names}.
+For more information on DNS host naming, see @ref{Host Names}.
--- manual/syslog.texi 2006-11-10 22:10:22.000000000 +0100
+++ manual/syslog.texi 2007-10-07 20:43:10.000000000 +0200
@@ -92,3 +92,3 @@ This tells how important the content of
defined priority values are: debug, informational, warning, critical.
-For the complete list, @xref{syslog; vsyslog}. Except for
+For the complete list, see @ref{syslog; vsyslog}. Except for
the fact that the priorities have a defined order, the meaning of each
--- manual/time.texi 2006-11-10 22:10:22.000000000 +0100
+++ manual/time.texi 2007-10-07 20:43:10.000000000 +0200
@@ -214,3 +214,3 @@ same value approximately every 72 minute
For additional functions to examine a process' use of processor time,
-and to control it, @xref{Resource Usage And Limitation}.
+and to control it, see @ref{Resource Usage And Limitation}.
============================================================
Index: manual/string.texi
--- manual/string.texi 3 Dec 2006 22:55:13 -0000 1.73
+++ manual/string.texi 27 Oct 2007 16:27:40 -0000
@@ -654,7 +654,7 @@ and @samp{bar} to produce @samp{foobar},
This function is not part of the ISO or POSIX standards, and is not
customary on Unix systems, but we did not invent it either. Perhaps it
-comes from MS-DOG.
+comes from MS-DOS.
Its behavior is undefined if the strings overlap. The function is
declared in @file{string.h}.
============================================================
Index: manual/startup.texi
--- manual/startup.texi 10 Nov 2006 21:10:22 -0000 1.49
+++ manual/startup.texi 27 Oct 2007 16:27:40 -0000
@@ -309,9 +309,9 @@ character, since this is assumed to term
The value of an environment variable can be accessed with the
@code{getenv} function. This is declared in the header file
-@file{stdlib.h}. All of the following functions can be safely used in
-multi-threaded programs. It is made sure that concurrent modifications
-to the environment do not lead to errors.
+@file{stdlib.h}. Modifications of enviroment variables are not
+allowed in Multi-threaded programs. The @code{getenv} function
+can be safely used in multi-threaded programs.
@pindex stdlib.h
@comment stdlib.h
============================================================
Index: manual/libc.texinfo
--- manual/libc.texinfo 22 Oct 2007 05:00:45 -0000 1.96
+++ manual/libc.texinfo 27 Oct 2007 16:30:43 -0000
@@ -18,9 +18,9 @@
@comment %**end of header (This is for running Texinfo on a region.)
@c sold 0.06/1.09, print run out 21may96
-@set EDITION 0.11
-@set VERSION 2.7
-@set UPDATED 2007-09-09
+@set EDITION 0.12
+@set VERSION 2.8
+@set UPDATED 2007-10-27
@set ISBN 1-882114-55-8
@copying
--
Andreas Jaeger, Director Platform / openSUSE, aj@suse.de
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]
next reply other threads:[~2007-10-27 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 16:31 Andreas Jaeger [this message]
2007-10-28 1:54 ` Ulrich Drepper
2007-10-28 5:18 ` Andreas Jaeger
2007-10-28 5:21 ` Roland McGrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ve8so6y7.fsf@suse.de \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).