From 8b1f3f8e28008cf6c565f8376ddfe7af54931512 Mon Sep 17 00:00:00 2001 From: Mark Linimon Date: Mon, 24 May 2004 04:02:46 +0000 Subject: [PATCH] Change occurences of FreeBSD to &os; since I brought in those entities with my most recent changes. Suggested by: keramida Approved by: ceri (mentor) (implicitly) --- .../articles/problem-reports/article.sgml | 44 +++++++++---------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/en_US.ISO8859-1/articles/problem-reports/article.sgml b/en_US.ISO8859-1/articles/problem-reports/article.sgml index 75ad974a51..a34bec1589 100644 --- a/en_US.ISO8859-1/articles/problem-reports/article.sgml +++ b/en_US.ISO8859-1/articles/problem-reports/article.sgml @@ -11,7 +11,7 @@
- Writing FreeBSD Problem Reports + Writing &os; Problem Reports $FreeBSD$ @@ -27,7 +27,7 @@ This article describes how to best formulate and submit a - problem report to the FreeBSD Project. + problem report to the &os; Project. @@ -60,7 +60,7 @@ can be analyzed and dealt with swiftly, to the mutual satisfaction of both user and developer. - Although the primary focus of this article is on FreeBSD + Although the primary focus of this article is on &os; problem reports, most of it should apply quite well to other software projects. @@ -142,11 +142,11 @@ mailing lists, or recently was; it may even already be fixed in a newer version than what you are running. You should therefore check all the obvious places before submitting your problem - report. For FreeBSD, this means: + report. For &os;, this means: - The FreeBSD + The &os; Frequently Asked Questions (FAQ) list. The FAQ attempts to provide answers for a wide range of questions, @@ -166,7 +166,7 @@ lists—if you are not subscribed, use the - searchable archives on the FreeBSD web site. If your + searchable archives on the &os; web site. If your problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something you have overlooked. @@ -183,7 +183,7 @@ Next, the searchable - FreeBSD PR database (GNATS). Unless your problem + &os; PR database (GNATS). Unless your problem is recent or obscure, there is a fair chance it has already been reported. @@ -217,15 +217,15 @@ The first catch here is that if the problem is a bug in third-party software (a port or a package you have installed), you - should report the bug to the original author, not to the FreeBSD + should report the bug to the original author, not to the &os; Project. There are two exceptions to this rule: the first is if the bug does not occur on other platforms, in which case the - problem may lie in how the software was ported to FreeBSD; the + problem may lie in how the software was ported to &os;; the second is if the original author has already fixed the bug and released a patch or a new version of his software, and the - FreeBSD port has not been updated yet. + &os; port has not been updated yet. - The second catch is that FreeBSD's bug tracking system sorts + The second catch is that &os;'s bug tracking system sorts problem reports according to the category the originator selected. Therefore, if you select the wrong category when you submit your problem report, there is a good chance that it will @@ -237,7 +237,7 @@ Writing the problem report Now that you have decided that your issue merits a problem - report, and that it is a FreeBSD problem, it is time to write + report, and that it is a &os; problem, it is time to write the actual problem report. Before we get into the mechanics of the program used to generate and submit PRs, here are some tips and tricks to help make sure that your PR will be most @@ -445,8 +445,8 @@ tracking of problem reports. If you cannot post mail messages from the machine you're running &man.send-pr.1; on, your problem report will not reach the GNATS database. For details - on the setup of mail on FreeBSD, see the Electronic - Mail chapter of the FreeBSD Handbook at + on the setup of mail on &os;, see the Electronic + Mail chapter of the &os; Handbook at . @@ -475,7 +475,7 @@ base utilities, a patch against &os.current; (the HEAD CVS branch) is preferred since all new code should be applied and tested there first. After appropriate or substantial testing - has been done, the code will be merged/migrated to the STABLE + has been done, the code will be merged/migrated to the &os.stable; branch. If you attach a patch inline, instead of as an attachment, @@ -528,7 +528,7 @@ Submitter-Id: Do not change this. The default value of current-users is - correct, even if you run FreeBSD-STABLE. + correct, even if you run &os.stable;. @@ -548,7 +548,7 @@ Confidential: This is prefilled to no. Changing it makes no sense as - there is no such thing as a confidential FreeBSD problem + there is no such thing as a confidential &os; problem report—the PR database is distributed worldwide by CVSup. @@ -602,7 +602,7 @@ advocacy: problems relating to - FreeBSD's public image. Rarely used. + &os;'s public image. Rarely used. @@ -688,7 +688,7 @@ www: Changes or enhancements to - the FreeBSD website. + the &os; website. @@ -726,7 +726,7 @@ - Release: The version of FreeBSD + Release: The version of &os; that you are running. This is filled out automatically by &man.send-pr.1; and need only be changed if you are sending a problem report from a different system than the @@ -865,14 +865,14 @@ How to Report Bugs Effectively—an excellent - essay by Simon G. Tatham on composing useful (non-FreeBSD-specific) + essay by Simon G. Tatham on composing useful (non-&os;-specific) problem reports. Problem Report Handling Guidelines—valuable insight - into how problem reports are handled by the FreeBSD + into how problem reports are handled by the &os; developers.