MK> I'm assuming you worked out Yes, I figured out the right URL. MK> I don't understand your comment. The glibc web page links to MK> http://sources.redhat.com/bugzilla/ for the bugzilla -- which seems to MK> be an alias for the same bugzilla as soureware.org (or vice versa). MK> What's the problem?
Well, last week I had just submitted an item to the soureware.org URL. So when I see we are now supposed to submit to the redhat URL, I think "oh no, I wasted all my time submitting to this abandoned gas station in the desert or something". Upon further investigation I found the two are the same, but soureware.org is the canonical address. So please use the canonical address, http://sourceware.org/bugzilla/ . >> OK, looks good. So maybe now on the man pages just provide one >> hyperlink link to a bugs page, and then on that you can have one link for >> documentation bugs and one link for code bugs... I.e., one low >> maintenance link on the man pages, pointing to a very flexible bug >> instruction tree. MK> If I thought my advice was about filing kernel bugs was authoritative MK> , I'd make that change. But it is just my thoughts and advice -- and MK> creating a reference in each man page to a page that describes how MK> kernel bugs should be reported gives that advice more authority than MK> it currently deserves, IMO. OK, as long as there's some path from each man page to the new reporting_code_bugs page, though indirect. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
