about summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-03-08 11:05:57 +0000
committerUlrich Drepper <drepper@redhat.com>1999-03-08 11:05:57 +0000
commitb74656f98231fc1d31f8200b3306e2d821ec2cf4 (patch)
tree74354d8b8bdec4319a8aa4cd7be00e1d0babbeb1 /FAQ.in
parent598b5dc2d78268052a8ff16e76f0427adee14dba (diff)
downloadglibc-b74656f98231fc1d31f8200b3306e2d821ec2cf4.tar.gz
glibc-b74656f98231fc1d31f8200b3306e2d821ec2cf4.tar.xz
glibc-b74656f98231fc1d31f8200b3306e2d821ec2cf4.zip
Fix typo.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/FAQ.in b/FAQ.in
index 495e30c6af..91acca2063 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -1278,7 +1278,7 @@ When compiling new programs against glibc 2.1, you've got to specify the
 correct paths to the compiler (option -I with gcc) and linker (options
 --dynamic-linker, -L and --rpath).
 
-?	bonnie reports that char i/o with glibc 2 is much slower than with
+??	bonnie reports that char i/o with glibc 2 is much slower than with
 	libc5.  What can be done?
 
 {AJ} The GNU C library uses thread safe functions by default and libc5 used