Hi,

[EMAIL PROTECTED] wrote:
Package: manpages-dev
Version: 3.07-1
Severity: wishlist
File: /usr/share/man/man3/getopt.3.gz

Just looking at pages like the above, which I suppose is libc6
related, it is very hard to find out where to report bugs to. Yes,

This is true.

http://www.kernel.org/doc/man-pages/ is mentioned, but that is for
things wrong with the man page itself. But for bugs like "please
implement unsetting auto_abbrev like on Getopt::Long.3perl" the real
place to learn where to send bugs is (my guess:)
/usr/share/doc/libc6/BUGS and thus http://sourceware.org/bugzilla/ ,

Yes, that's the right place.

but one could never figure that out just looking at
/usr/share/man/man3/getopt.3.gz ! Therefore there is a whole class of
man pages that don't say the real party to contact.

The "real party" that I want people to contact here is the
documentation maintainer -- i.e., me -- but that is for
*documentation* bugs.  Once upon a time, there was no COLOPHON,
and people didn't know where to report documentation bugs.
(and in response to your bug, I now added the word
"documentation" to the COLPHON to make it clear that
the referred-to website is only for information about
reporting documentation bugs.

Reporting code problems is more difficult.  Yes, if it's a system
call bug raise a bug at the kernel.org bugzilla, and if it's a glibc
bug, then raise a bug at sourceware.org.  But those paths often *won't*
gain quick traction, since what is really required is to CC relevant
individuals on the report.  And finding those individuals requires
some effort -- e.g., looking for names in the source, or looking
in the VCS to see who touched the relevant source files.  In the
man pages, I can't practically identify those individuals for
each documented interface.

Cheers,

Michael

--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to