On Wed, Sep 3, 2008 at 8:35 PM, <[EMAIL PROTECTED]> wrote: > MK> Reporting code problems is more difficult. Yes, if it's a system > MK> call bug raise a bug at the kernel.org bugzilla, and if it's a glibc > MK> bug, then raise a bug at sourceware.org. > > So perhaps on pages of section 2 of the manual, paste the system call > address as where to report _code_ problem, and section 3, the > sourceware.org address.
Well, as I tried to indicate below, it's not usually as simple as that, and posting advice as simple as that would be misleading, IMO. > If indeed those are still the right sections > like they were back in '82. "back in 82"? > MK> But those paths often *won't* gain quick traction, since what is > MK> really required is to CC relevant individuals on the report. And > MK> finding those individuals requires some effort -- e.g., looking > MK> for names in the source, or looking in the VCS to see who touched > MK> the relevant source files. In the man pages, I can't practically > MK> identify those individuals for each documented interface. > > MK> Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ > MK> man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html > MK> Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html > ^_documentation_ I think that is fairly (okay, in fact: very) obvious from the context. > Anyway, just a Debian now has public relations officers etc. You/We've > got to think of this from the Customer Relations perspective, even > though nobody's getting paid. Well, I'm not part of Debian. On the other hand, I do for the moment get paid. > Anyway, compare a coreutils page with a full bug address, and a Linux > page, which is more like a dollar bill, with no address for problems, > like "if you the user knew what you were doing, you would know what to > do with bugs, so you might as well just turn off the computer now." I really don't get this at all. Sure, coreutils man pages provide a bug reporting address -- and no information about how to usefully report a bug. (And, as a consequence, I'd guess that they get more junk bug reports than they should.) I don't believe this is better than showing a hyperlink that leads to a page that describes how to report a bug and provides an email address to do so. > Anyway, so now the pages will say for documentation bugs do... begging > the question "what about for other bugs, no just documentation bugs, > which only account for 10%". OK, something to think about. As I said, there is no easy solution. I'll think about this a little more. -- 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]
