[Bug libc/5120] New: glibcbug still mentioned in documentation

["peter dot moulder at infotech dot monash dot edu dot au" <sourceware-bugzilla at sourceware dot org>]

The command

  grep -rl glibcbug . | grep -v ChangeLog

from glibc source directory still finds many matches [many in v2.6.1, and I've
checked that at least two erroneous occurrences persist in CVS].

Now that there is no glibcbug shell script (since 2004 according to
ChangeLog.14), these should be changed to reference
http://www.gnu.org/software/libc/bugs.html instead (as per README).

For the po files, all but one match (in v2.6.1 at least) is spurious (i.e.
caused by out-of-date msgid).  You can use

  perl -e '$/ = ""; while(<>) { print $ARGV, "\n", $_ if /glibcbug/ && !/msgid
".*glibcbug.*"/; }' po/*.po

to find the one non-spurious instance (po/nl.po in the case of v2.6.1).


Btw, a sentence was munged in r1.115 of FAQ.in in the paragraph beginning
`plenty of time'.  The words `i?86-linux takes approximately' should be re-added
after the word `for' at the end of the first line.

pjrm.

-- 
           Summary: glibcbug still mentioned in documentation
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: peter dot moulder at infotech dot monash dot edu dot au
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5120

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.