|
Bugzilla – Full Text Bug Listing |
| Summary: | gcc's internal errors should point to http://www.opensuse.org/Bugs:gcc | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michal Marek <mmarek> |
| Component: | Basesystem | Assignee: | GCC Development Team at SuSE <development-gcc> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | kukuk |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
I'm not sure opensuse.org is appropriate for the SLES system compiler, though. So, Mr. Project Manager, suggest something ;) I don't know. If this is something project managers have to decide, then forget about it... Gerald, your job to come up with something - otherwise it stays as it is. I mean: It goes to http://www.opensuse.org/Bugs:gcc . What was the decision about the comments we have in the various shell scripts where we used to refer to feedback@suse.de in that past? Does anyone know/remember? I'd suggest to do more or less the same here. Don't use any adress there. We don't have a feedback channel anymore. Since we modify GCC, and bug reports against our GCC might go to the FSF project and cause stirrup there if we don't provide a URL, I guess it's best to use the opensuse.org URL then. Could we just make the disclaimer At this time, the public Bugzilla is not intended for the enterprise products. at http://www.opensuse.org/Submit_a_bug#Reporting_a_Bug a bit better visible (by making it a paragraph of its own or italics or so)? I'd say it'd be rather easy to apply differing patches based on whether we're build for business products or not. The only question would then be where to point sles users to. Fixed in 10.2 Alpha4. |
gcc on SUSE prints See <URL:http://www.suse.de/feedback> for instructions. on internal compiler errors (bug-reporting.patch). This confuses users, because there are no gcc-specific instruction on that url (see today's bug #135621 for instance). Changing it to http://www.opensuse.org/Bugs:gcc would a better choice IMHO.