From 18c34beb3790c8a002ae15b4a25185ebaafd5248 Mon Sep 17 00:00:00 2001 From: Ceri Davies Date: Sun, 25 May 2003 21:23:08 +0000 Subject: [PATCH] Various grammatical improvements. --- .../articles/pr-guidelines/article.sgml | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/en_US.ISO8859-1/articles/pr-guidelines/article.sgml b/en_US.ISO8859-1/articles/pr-guidelines/article.sgml index 634c46d156..e29f3295d8 100644 --- a/en_US.ISO8859-1/articles/pr-guidelines/article.sgml +++ b/en_US.ISO8859-1/articles/pr-guidelines/article.sgml @@ -331,9 +331,9 @@ GNATS is picky about the format of a submitted bug report. This is why a lot of PRs end up being misfiled if - the submitter forgets to fill a field or puts the wrong sort of - data some of the PR fields. This section aims to provide most - of the necessary details for FreeBSD developers that can help + the submitter forgets to fill in a field or puts the wrong sort of + data in some of the PR fields. This section aims to provide most + of the necessary details for FreeBSD developers that can help them to close or refile these PRs. When GNATS cannot deduce what to do with a problem report @@ -341,7 +341,7 @@ gnats-admin and files it under the pending category. This is now a misfiled PR and will not appear in bug report - listings, unless someone explicitly asks a list of all the + listings, unless someone explicitly asks for a list of all the misfiled PRs. If you have access to the FreeBSD cluster machines, you can use query-pr to view a listing of PRs that have been misfiled: @@ -363,7 +363,7 @@ - When filling the &man.send-pr.1; template, the submitter + When completing the &man.send-pr.1; template, the submitter forgot to set the category or class of the PR to a proper value. @@ -444,7 +444,7 @@ This was misfiled because the subject didn't have the format: PRs misfiled because of missing fields The second type of misfiled PRs is usually the result of a - submitter who forgot to fill all the necessary fields when + submitter forgetting to fill all the necessary fields when writing the original PR. Missing or bogus category or @@ -456,7 +456,7 @@ This was misfiled because the subject didn't have the format: Another common cause of misfiled PRs because of formatting issues is quoting, changes or removal of the send-pr template, either by the user who - edits the template or by mailers who do strange things to + edits the template or by mailers which do strange things to plain text messages. This doesn't happen a lot of the time, but it can be fixed with edit-pr too; it does require a bit of work from the developer who refiles the @@ -466,17 +466,17 @@ This was misfiled because the subject didn't have the format:
Misfiled PRs that are not really problem reports - Some times a user wants to submit a report for a problem + Sometimes a user wants to submit a report for a problem and sends a simple email message to GNATS. The GNATS scripts will recognize bug reports that are formatted using the &man.send-pr.1; template. They cannot parse any sort of email - though. This is why submissions of bug reports that are send + though. This is why submissions of bug reports that are sent to freebsd-gnats-submit@freebsd.org have to - follow the template of send-pr but email - reports sent to &a.bugs;. + follow the template of send-pr, but email + reports can be sent to &a.bugs;. - Developers that come across PRs that look like they should - be posted to &a.bugs.name; or some other list should close the + Developers that come across PRs that look like they should have + been posted to &a.bugs.name; or some other list should close the PR, informing the submitter in their state-change log why this is not really a PR and where the message should be posted. @@ -491,18 +491,18 @@ This was misfiled because the subject didn't have the format: the sender's address of spam mail is never valid these days. Bounces will come back for each PR that is closed. - Currently, with the installation of some antispam filters, + Currently, with the installation of some antispam filters that check all submissions to the GNATS database, the amount of spam that reaches the pending state is very small. All developers who have access to the FreeBSD.org cluster - machines are encouraged to check for misfiled PRs immediately + machines are encouraged to check for misfiled PRs and immediately close those that are spam mail. Whenever you close one of these PRs it is also a good idea to set its category to junk. Junk PRs are not backed up, so filing spam mail under this category makes it - obvious that we do not care to keep around and waste disk + obvious that we do not care to keep it around or waste disk space for it.