This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: How to report doc bugs and/or kernel ABI update?
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
- Cc: mtk dot manpages at gmail dot com, libc-alpha at sourceware dot org
- Date: Thu, 19 Apr 2012 12:20:22 -0400
- Subject: Re: How to report doc bugs and/or kernel ABI update?
- References: <4F902909.10703@gmail.com>
2012/4/19 KOSAKI Motohiro <kosaki.motohiro@gmail.com>:
> Hello,
>
> I'm not sure this is proper mailing list or not. but I hope to ask the community.
> When finding the man page bugs and/or finding/creating kernel ABI change commits, I offten
> request man change to Michael by using bugzilla.kernel.org. and, I'm sorry, I neglected
> glibc info because, I'm sorry again, I didn't realized it still be maintained.
>
> So, I'd like to ask (or discuss) proper reporting way when I (or other person) make a kernel ABI change.
> It would be nice if glibc wiki has a guide of reporting documentation bugs.
Documentation bugs for the glibc manual should be reported via the
glibc bugzilla.
http://www.gnu.org/software/libc/bugs.html
You should use product=glibc, component=manual.
When in doubt you can start asking questions on
libc-help@sourceware.org, and then file a bug.
Cheers,
Carlos.