Examples of using Problem report in English and their translations into Portuguese
{-}
-
Colloquial
-
Official
-
Medicine
-
Financial
-
Ecclesiastic
-
Ecclesiastic
-
Computer
-
Official/political
Before submitting a problem report, read Writing FreeBSD Problem Reports,
Read the entire document before submitting a problem report, rather than treating it as a step-by-step tutorial.
Giving a good description in the summary of the problem report makes the work of port committers a lot easier.
As noted above, if your problem report includes a patch,
When a problem report has not received attention after several weeks,
This article describes how to best formulate and submit a problem report to the FreeBSD Project.
not all of them should engender a problem report.
Some cases where it may be appropriate to submit a problem report about something that is not a bug are.
A good rule to follow is to always do a background search before submitting a problem report.
review the Writing the problem report section in the Problem Reports article.
code submitted through a problem report.
A good rule to follow is to always do a background search before submitting a problem report.
submit a problem report and include output from the above tools.
however it requires 36 hours of graduate credit and a problem report followed by a public lecture.
For technical support, send an email with a problem report that you have generated from Metalix products.
There are few things that will annoy a developer more than receiving a problem report about a bug she has already fixed.
This article describes how to best formulate and submit a problem report to the FreeBSD Project.
If you cannot post mail messages from the machine you are running send-pr(1) on, your problem report will not reach the GNATS database.
Now that you have decided that your issue merits a problem report, and that it is a FreeBSD problem,
A problem report is closed when any changes have been integrated,