svn commit: r39486 - head/en_US.ISO8859-1/articles/problem-reports

[Eitan Adler]

Author: eadler (src,ports committer)
Date: Sun Sep  2 02:59:41 2012
New Revision: 39486
URL: http://svn.freebsd.org/changeset/doc/39486

Log:
  Move priority and severity into the "email template only section"
  
  Approved by:	wblock

Modified:
  head/en_US.ISO8859-1/articles/problem-reports/article.sgml

Modified: head/en_US.ISO8859-1/articles/problem-reports/article.sgml
==============================================================================
--- head/en_US.ISO8859-1/articles/problem-reports/article.sgml	Sat Sep  1 15:01:58 2012	(r39485)
+++ head/en_US.ISO8859-1/articles/problem-reports/article.sgml	Sun Sep  2 02:59:41 2012	(r39486)
@@ -646,7 +646,7 @@
 	adding one or more email addresses to the
 	<literal>Cc:</literal> header.</para>
 
-      <para>In the email template you will find the following two
+      <para>In the email template only, you will find the following
 	single-line fields:</para>
 
       <itemizedlist>
@@ -664,6 +664,47 @@
 	    <application>CVSup</application>.</para>
 	</listitem>
 
+	<listitem>
+	  <para><emphasis>Severity:</emphasis> One of
+	    <literal>non-critical</literal>,
+	    <literal>serious</literal> or
+	    <literal>critical</literal>.  Do not overreact; refrain
+	    from labeling your problem <literal>critical</literal>
+	    unless it really is (e.g. data corruption issues, serious
+	    regression from previous functionality in -CURRENT)
+	    or <literal>serious</literal> unless
+	    it is something that will affect many users (kernel
+	    panics or freezes; problems with
+	    particular device drivers or system utilities).  &os;
+	    developers will not necessarily work on your problem faster
+	    if you inflate its importance since there are so many other
+	    people who have done exactly that &mdash; in fact, some
+	    developers pay little attention to this field
+	    because of this.</para>
+
+	  <note>
+	    <para>Major security problems should <emphasis>not</emphasis>
+	      be filed in GNATS, because all GNATS information is public
+	      knowledge.  Please send such problems in private email to
+	      &a.security-officer;.</para>
+	  </note>
+	</listitem>
+
+	<listitem>
+	  <para><emphasis>Priority:</emphasis> One of
+	    <literal>low</literal>, <literal>medium</literal> or
+	    <literal>high</literal>.  <literal>high</literal> should
+	    be reserved for problems that will affect practically
+	    every user of &os; and <literal>medium</literal> for
+	    something that will affect many users.</para>
+
+	  <note>
+	    <para>This field has become so widely abused that it is
+	      almost completely meaningless.</para>
+	  </note>
+	</listitem>
+
+
       </itemizedlist>
 
       <para>The next section describes fields that are common to both
@@ -715,46 +756,6 @@
 	</listitem>
 
 	<listitem>
-	  <para><emphasis>Severity:</emphasis> One of
-	    <literal>non-critical</literal>,
-	    <literal>serious</literal> or
-	    <literal>critical</literal>.  Do not overreact; refrain
-	    from labeling your problem <literal>critical</literal>
-	    unless it really is (e.g. data corruption issues, serious
-	    regression from previous functionality in -CURRENT)
-	    or <literal>serious</literal> unless
-	    it is something that will affect many users (kernel
-	    panics or freezes; problems with
-	    particular device drivers or system utilities).  &os;
-	    developers will not necessarily work on your problem faster
-	    if you inflate its importance since there are so many other
-	    people who have done exactly that &mdash; in fact, some
-	    developers pay little attention to this field
-	    because of this.</para>
-
-	  <note>
-	    <para>Major security problems should <emphasis>not</emphasis>
-	      be filed in GNATS, because all GNATS information is public
-	      knowledge.  Please send such problems in private email to
-	      &a.security-officer;.</para>
-	  </note>
-	</listitem>
-
-	<listitem>
-	  <para><emphasis>Priority:</emphasis> One of
-	    <literal>low</literal>, <literal>medium</literal> or
-	    <literal>high</literal>.  <literal>high</literal> should
-	    be reserved for problems that will affect practically
-	    every user of &os; and <literal>medium</literal> for
-	    something that will affect many users.</para>
-
-	  <note>
-	    <para>This field has become so widely abused that it is
-	      almost completely meaningless.</para>
-	  </note>
-	</listitem>
-
-	<listitem>
 	  <para><emphasis>Category:</emphasis> Choose an appropriate
 	    category.</para>