|
Bugzilla – Full Text Bug Listing |
| Summary: | broken link: no frobnicate in glibc-html | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Christopher Yeleighton <giecrilj> |
| Component: | Development | Assignee: | Michael Matz <matz> |
| Status: | RESOLVED UPSTREAM | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | aj, ke, pth |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christopher Yeleighton
2010-11-06 23:52:59 UTC
See also <URL:https://features.opensuse.org/310801#>. Christopher, you should report such a bug uptreams and the rebort the bug number here. _ _ _ If the glibc you are using comes from a complete operating system distribution, you should report bugs to that distribution project first. Your distribution's own documentation and web pages should refer you to their bug-reporting system. Your distribution's maintainers will determine whether the problem is specific to their modifications or other details of that particular system. If the problem does exist in the standard GNU C Library code, they will report it to the GNU maintainers or direct you how to do so. _ _ _ <URL: http://www.gnu.org/software/libc/bugs.html#what_to_report > Accordingly, since I am not a maintainer, if you want me to report bugs regarding glibc upstream, I need a specific recommendation for each and every bug separately. No, you don't need a recommendation, so please report this upstream. |