manual: Drop obsolete @refill

The @refill command has been obsolete for a while and now texinfo has
started warning about it.

Reviewed-by: Florian Weimer <fweimer@redhat.com>
Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>

manual/contrib.texi

@@ -525,7 +525,7 @@ The random number generation functions @code{random}, @code{srandom},
 for the University of California at Berkeley and are copyrighted by the
 Regents of the University of California.  They have undergone minor
 changes to fit into @theglibc{} and to fit the @w{ISO C} standard,
-but the functional code is Berkeley's.@refill
+but the functional code is Berkeley's.
 
 @item
 The Internet-related code (most of the @file{inet} subdirectory) and

manual/creature.texi

@@ -9,7 +9,7 @@ If you compile your programs using @samp{gcc -ansi}, you get only the
 @w{ISO C} library features, unless you explicitly request additional
 features by defining one or more of the feature macros.
 @xref{Invoking GCC,, GNU CC Command Options, gcc, The GNU CC Manual},
-for more information about GCC options.@refill
+for more information about GCC options.
 
 You should define these macros by using @samp{#define} preprocessor
 directives at the top of your source code files.  These directives

manual/ctype.texi

@@ -57,7 +57,7 @@ character argument is passed as an @code{int}, and it may be the
 constant value @code{EOF} instead of a real character.
 
 The attributes of any given character can vary between locales.
-@xref{Locales}, for more information on locales.@refill
+@xref{Locales}, for more information on locales.
 
 These functions are declared in the header file @file{ctype.h}.
 @pindex ctype.h
@@ -265,7 +265,7 @@ bits.  This function is a BSD extension and is also an SVID extension.
 @standards{SVID, ctype.h}
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 This is identical to @code{tolower}, and is provided for compatibility
-with the SVID.  @xref{SVID}.@refill
+with the SVID.  @xref{SVID}.
 @end deftypefun
 
 @deftypefun int _toupper (int @var{c})

manual/intro.texi

@@ -99,7 +99,7 @@ by the International Standardization Organization (ISO):
 We here refer to the standard as @w{ISO C} since this is the more
 general standard in respect of ratification.
 The header files and library facilities that make up @theglibc{} are
-a superset of those specified by the @w{ISO C} standard.@refill
+a superset of those specified by the @w{ISO C} standard.
 
 @pindex gcc
 If you are concerned about strict adherence to the @w{ISO C} standard, you
@@ -144,7 +144,7 @@ general, the additional requirements and functionality defined by the
 POSIX standards are aimed at providing lower-level support for a
 particular kind of operating system environment, rather than general
 programming language support which can run in many diverse operating
-system environments.@refill
+system environments.
 
 @Theglibc{} implements all of the functions specified in
 @cite{ISO/IEC 9945-1:1996, the POSIX System Application Program
@@ -1035,7 +1035,7 @@ feature test macro definition (@pxref{Feature Test Macros}).
 
 For more information about the use of header files and @samp{#include}
 directives, @pxref{Header Files,,, cpp.info, The GNU C Preprocessor
-Manual}.@refill
+Manual}.
 
 @Theglibc{} provides several header files, each of which contains
 the type and macro definitions and variable and function declarations

manual/lang.texi

@@ -459,7 +459,7 @@ was invoked with the same @var{ap} argument.
 
 In @theglibc{}, @code{va_end} does nothing, and you need not ever
 use it except for reasons of portability.
-@refill
+
 @end deftypefn
 
 Sometimes it is necessary to parse the list of parameters more than once

manual/maint.texi

@@ -52,7 +52,7 @@ complete file names, such as @file{strlen.c}).  Use @code{routines} for
 modules that define functions in the library, and @code{aux} for
 auxiliary modules containing things like data definitions.  But the
 values of @code{routines} and @code{aux} are just concatenated, so there
-really is no practical difference.@refill
+really is no practical difference.
 
 @item tests
 The names of test programs for this section of the library.  These
@@ -70,7 +70,7 @@ indicates a bug in the library or error in building.
 The names of ``other'' programs associated with this section of the
 library.  These are programs which are not tests per se, but are other
 small programs included with the library.  They are built by
-@w{@samp{make others}}.@refill
+@w{@samp{make others}}.
 
 @item install-lib
 @itemx install-data
@@ -82,7 +82,7 @@ Files to be installed by @w{@samp{make install}}.  Files listed in
 installed in the directory specified by @samp{datadir} in
 @file{configparms} or @file{Makeconfig}.  Files listed in @code{install}
 are installed in the directory specified by @samp{bindir} in
-@file{configparms} or @file{Makeconfig}.@refill
+@file{configparms} or @file{Makeconfig}.
 
 @item distribute
 Other files from this subdirectory which should be put into a
@@ -337,7 +337,7 @@ subdirectory, it lists other subdirectories of @file{sysdeps} which are
 appended to the list, appearing after the subdirectory containing the
 @file{Implies} file.  Lines in an @file{Implies} file that begin with a
 @samp{#} character are ignored as comments.  For example,
-@file{unix/bsd/Implies} contains:@refill
+@file{unix/bsd/Implies} contains:
 @smallexample
 # BSD has Internet-related things.
 unix/inet
@@ -388,7 +388,7 @@ operating system-dependent version of it, move the file into
 @file{sysdeps/generic} and write your new implementation in the
 appropriate system-specific subdirectory.  Note that if a file is to be
 system-dependent, it @strong{must not} appear in one of the main source
-directories.@refill
+directories.
 
 There are a few special files that may exist in each subdirectory of
 @file{sysdeps}:
@@ -408,7 +408,7 @@ the library.  It can also set the @code{make} variable
 @samp{sysdep-routines}, to specify extra modules to be included in the
 library.  You should use @samp{sysdep-routines} rather than adding
 modules to @samp{routines} because the latter is used in determining
-what to distribute for each subdirectory of the main source tree.@refill
+what to distribute for each subdirectory of the main source tree.
 
 Each makefile in a subdirectory in the ordered list of subdirectories to
 be searched is included in order.  Since several system-dependent
@@ -433,7 +433,7 @@ files that should go into the library for the system this subdirectory
 of @file{sysdeps} implements.  For example,
 @file{sysdeps/unix/inet/Subdirs} contains @file{inet}; the @file{inet}
 directory contains various network-oriented operations which only make
-sense to put in the library on systems that support the Internet.@refill
+sense to put in the library on systems that support the Internet.
 
 @item configure
 
@@ -625,7 +625,7 @@ partially defines them; a @file{sysdep.h} file in another directory must
 finish defining them for the particular machine and operating system
 variant.  See @file{sysdeps/unix/sysdep.h} and the machine-specific
 @file{sysdep.h} implementations to see what these macros are and what
-they should do.@refill
+they should do.
 
 The system-specific makefile for the @file{unix} directory
 (@file{sysdeps/unix/Makefile}) gives rules to generate several files

manual/memory.texi

@@ -2796,7 +2796,7 @@ To illustrate this, suppose you have a function
 fails.  If the file cannot be opened, it prints an error message and
 jumps out to the command level of your program using @code{longjmp}.
 Let's change @code{open2} (@pxref{Alloca Example}) to use this
-subroutine:@refill
+subroutine:
 
 @smallexample
 int

manual/setjmp.texi

@@ -136,7 +136,7 @@ This function restores current execution to the state saved in
 established that return point.  Returning from @code{setjmp} by means of
 @code{longjmp} returns the @var{value} argument that was passed to
 @code{longjmp}, rather than @code{0}.  (But if @var{value} is given as
-@code{0}, @code{setjmp} returns @code{1}).@refill
+@code{0}, @code{setjmp} returns @code{1}).
 @end deftypefun
 
 There are a lot of obscure but important restrictions on the use of

manual/stdio.texi

@@ -2532,7 +2532,7 @@ obstack @var{obstack} to allocate the space.  @xref{Obstacks}.
 
 The characters are written onto the end of the current object.
 To get at them, you must finish the object with @code{obstack_finish}
-(@pxref{Growing Objects}).@refill
+(@pxref{Growing Objects}).
 @end deftypefun
 
 @node Variable Arguments Output
@@ -2696,7 +2696,7 @@ variable argument list specified directly as for @code{vprintf}.
 @c inconsistent state in case of cancellation.
 The @code{obstack_vprintf} function is the equivalent of
 @code{obstack_printf} with the variable argument list specified directly
-as for @code{vprintf}.@refill
+as for @code{vprintf}.
 @end deftypefun
 
 Here's an example showing how you might use @code{vfprintf}.  This is a

manual/string.texi

@@ -1921,7 +1921,7 @@ strcasestr ("hello, World", "wo")
 This is like @code{strstr}, but @var{needle} and @var{haystack} are byte
 arrays rather than strings.  @var{needle-len} is the
 length of @var{needle} and @var{haystack-len} is the length of
-@var{haystack}.@refill
+@var{haystack}.
 
 This function is a GNU extension.
 @end deftypefun