glibc manual on www.gnu.org is out of date

[Collin Funk]

Bruno Haible <bruno@clisp.org> writes:

> Collin Funk wrote:
>> > The glibc manual at
>> >   https://www.gnu.org/software/libc/manual/html_node/index.html
>> > is out-of-date (still version 2.38). Whereas the one at
>> >   https://sourceware.org/glibc/manual/latest/html_node/index.html
>> >   https://sourceware.org/glibc/manual/2.42/html_node/index.html
>> > is up-to-date.
>> >
>> > Could the one on gnu.org be updated, please?
>> 
>> I assume the gnu.org link was indexed by Google or some other search
>> engine?
>> 
>> The links on https://www.gnu.org/software/libc/ under documentation link
>> to https://sourceware.org/glibc/manual/ where the updated manuals are.
>> 
>> That seems better than having to maintain both, in my opinion.
>
> I am asking for three reasons:
>
>   * GNU Gnulib's documentation has hundreds of references to the GNU libc
>     manual. I don't really want to change n*100 hyperlinks to refer to
>     a host owned by Red Hat when the same documentation ought to be
>     available on www.gnu.org.
>
>   * When a Texinfo source file contains a reference
>       @ref{Something,,Something,libc}
>     the conversion to HTML by 'makeinfo' will create a hyperlink to
>       https://www.gnu.org/software/libc/manual/html_node/Something.html
>
>   * The instructions that every GNU package receives when it becomes a
>     GNU package include these two paragraphs:
>
>       Please write or update the web pages about the program, to put in
>       https://www.gnu.org/software/<PACKAGE>.  These pages should be the
>       main web site for the program, and they should really have the
>       information for users, not just a link to another site; please use
>       https://www.gnu.org/software/<PACKAGE> whenever you give out the URL
>       for the home page of the program.  Please don't set up a "site for the
>       program" anywhere else--if you want to do work on additional web pages
>       about the program, please put them on www.gnu.org.
>
>       (It is ok to put pages that address developers-only topics on another
>       site, and likewise for pages that access databases.)

Good points. I did not consider the use of @ref{...,libc}. That is alone
is reason enough to upload them, in my opinion.

Adding Carlos to CC. Could you please upload them? I cannot since I am
not a member of the Savannah group.

Collin