On 29 July 2010 23:14, Bruno Haible <br...@clisp.org> wrote: > Reuben Thomas wrote: >> Thanks. I guess I should report this documentation bug somewhere, but >> where? (As mentioned in a recent message to this list, I've not had >> much mileage from reporting similar things to glibc in the past.) > > The place to report it is glibc bugzilla <http://sourceware.org/bugzilla/>. > For documentation bugs, if you want to get them fixed, you need to provide > a patch in unidiff or git format and a ChangeLog entry. And be patient > afterwards.
Since my first bug report was 6 years ago and the second was 4 years ago, I suspect my lack of a patch was the issue. I shall see if I can dig out the old reports and make a combined patch, since I think it was all just patches to fix comments in regex.h. -- http://rrt.sc3d.org
