mirror of
git://sourceware.org/git/glibc.git
synced 2025-01-30 12:31:53 +08:00
manual: fix doubled-words and typos
* manual/charset.texi (Selecting the Conversion): Likewise. * manual/errno.texi (Error Messages): Likewise. * manual/getopt.texi (Getopt Long Options): Likewise. * manual/memory.texi (Resizing the Data Segment): Likewise. * manual/message.texi (GUI program problems): Likewise. * manual/resource.texi (CPU Affinity): Likewise. * manual/stdio.texi (Streams and Threads): Likewise. * manual/time.texi (High Accuracy Clock): Likewise.
This commit is contained in:
parent
34a407de96
commit
bbf70ae9ce
11
ChangeLog
11
ChangeLog
@ -1,3 +1,14 @@
|
||||
2010-02-22 Jim Meyering <meyering@redhat.com>
|
||||
|
||||
* manual/errno.texi (Error Messages): Fix doubled-words and typos.
|
||||
* manual/charset.texi (Selecting the Conversion): Likewise.
|
||||
* manual/getopt.texi (Getopt Long Options): Likewise.
|
||||
* manual/memory.texi (Resizing the Data Segment): Likewise.
|
||||
* manual/message.texi (GUI program problems): Likewise.
|
||||
* manual/resource.texi (CPU Affinity): Likewise.
|
||||
* manual/stdio.texi (Streams and Threads): Likewise.
|
||||
* manual/time.texi (High Accuracy Clock): Likewise.
|
||||
|
||||
2009-02-20 David S. Miller <davem@davemloft.net>
|
||||
|
||||
* sysdeps/sparc/sparc32/dl-machine.h (elf_machine_runtime_setup):
|
||||
|
@ -393,7 +393,7 @@ We already said above that the currently selected locale for the
|
||||
by the functions we are about to describe. Each locale uses its own
|
||||
character set (given as an argument to @code{localedef}) and this is the
|
||||
one assumed as the external multibyte encoding. The wide character
|
||||
character set always is UCS-4, at least on GNU systems.
|
||||
set always is UCS-4, at least on GNU systems.
|
||||
|
||||
A characteristic of each multibyte character set is the maximum number
|
||||
of bytes that can be necessary to represent one character. This
|
||||
|
@ -1425,7 +1425,7 @@ available on all systems implementing @w{ISO C}. But often the text
|
||||
@code{perror} generates is not what is wanted and there is no way to
|
||||
extend or change what @code{perror} does. The GNU coding standard, for
|
||||
instance, requires error messages to be preceded by the program name and
|
||||
programs which read some input files should should provide information
|
||||
programs which read some input files should provide information
|
||||
about the input file name and the line number in case an error is
|
||||
encountered while reading the file. For these occasions there are two
|
||||
functions available which are widely used throughout the GNU project.
|
||||
|
@ -269,7 +269,7 @@ When @code{getopt_long} has no more options to handle, it returns
|
||||
@var{argv} of the next remaining argument.
|
||||
@end deftypefun
|
||||
|
||||
Since long option names were used before before the @code{getopt_long}
|
||||
Since long option names were used before the @code{getopt_long}
|
||||
options was invented there are program interfaces which require programs
|
||||
to recognize options like @w{@samp{-option value}} instead of
|
||||
@w{@samp{--option value}}. To enable these programs to use the GNU
|
||||
|
@ -2379,7 +2379,7 @@ exceed the process' data storage limit.
|
||||
@c The Brk system call in Linux (as opposed to the GNU C Library function)
|
||||
@c is considerably different. It always returns the new end of the data
|
||||
@c segment, whether it succeeds or fails. The GNU C library Brk determines
|
||||
@c it's a failure if and only if if the system call returns an address less
|
||||
@c it's a failure if and only if the system call returns an address less
|
||||
@c than the address requested.
|
||||
|
||||
@end deftypefun
|
||||
|
@ -1466,7 +1466,7 @@ have this problem. But there is a very simple and powerful method to
|
||||
handle these kind of problems with the @code{gettext} functions.
|
||||
|
||||
@noindent
|
||||
As as example consider the following fictional situation. A GUI program
|
||||
As an example consider the following fictional situation. A GUI program
|
||||
has a menu bar with the following entries:
|
||||
|
||||
@smallexample
|
||||
|
@ -1288,7 +1288,7 @@ protected from concurrent accesses from different processors.
|
||||
The POSIX standard up to this date is of not much help to solve this
|
||||
problem. The Linux kernel provides a set of interfaces to allow
|
||||
specifying @emph{affinity sets} for a process. The scheduler will
|
||||
schedule the thread or process on on CPUs specified by the affinity
|
||||
schedule the thread or process on CPUs specified by the affinity
|
||||
masks. The interfaces which the GNU C library define follow to some
|
||||
extend the Linux kernel interface.
|
||||
|
||||
|
@ -574,7 +574,7 @@ operation itself is avoided. More importantly, functions like
|
||||
introduction of threads) were implemented as macros which are very fast
|
||||
if the buffer is not empty. With the addition of locking requirements
|
||||
these functions are no longer implemented as macros since they would
|
||||
would expand to too much code.
|
||||
expand to too much code.
|
||||
But these macros are still available with the same functionality under the new
|
||||
names @code{putc_unlocked} and @code{getc_unlocked}. This possibly huge
|
||||
difference of speed also suggests the use of the @code{_unlocked}
|
||||
|
@ -972,7 +972,7 @@ This counter represents the number of calibration errors (caused by
|
||||
large offsets or jitter).
|
||||
|
||||
@item long int stbcnt
|
||||
This counter denotes the number of of calibrations where the stability
|
||||
This counter denotes the number of calibrations where the stability
|
||||
exceeded the threshold.
|
||||
@end table
|
||||
@end deftp
|
||||
|
Loading…
Reference in New Issue
Block a user