svn commit: r45150 - head/en_US.ISO8859-1/articles/pr-guidelines

[Eitan Adler]

Author: eadler
Date: Sun Jun 29 07:40:22 2014
New Revision: 45150
URL: http://svnweb.freebsd.org/changeset/doc/45150

Log:
  Remove further references to things which don't happen without GNATS

Modified:
  head/en_US.ISO8859-1/articles/pr-guidelines/article.xml

Modified: head/en_US.ISO8859-1/articles/pr-guidelines/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/pr-guidelines/article.xml	Sun Jun 29 07:40:21 2014	(r45149)
+++ head/en_US.ISO8859-1/articles/pr-guidelines/article.xml	Sun Jun 29 07:40:22 2014	(r45150)
@@ -227,7 +227,7 @@
 	<para><link linkend="pr-stale">Stale PRs</link></para>
       </listitem>
       <listitem>
-	<para><link linkend="pr-misfiled">Misfiled PRs</link></para>
+	<para><link linkend="pr-misfiled-notpr">Non-Bug PRs</link></para>
       </listitem>
     </itemizedlist>
 
@@ -818,72 +818,6 @@
       </itemizedlist>
     </section>
 
-    <section xml:id="pr-misfiled">
-      <title>Misfiled PRs</title>
-
-      <para>GNATS is picky about the format of a submitted bug report.
-	This is why a lot of PRs end up being <quote>misfiled</quote> if
-	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.</para>
-
-      <para>When GNATS cannot deduce what to do with a problem report
-	that reaches the database, it sets the responsible of the PR to
-	<literal>gnats-admin</literal> and files it under the
-	<literal>pending</literal> category.  This is now a
-	<quote>misfiled</quote> PR and will not appear in bug report
-	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 <command>query-pr</command> to view a
-	listing of PRs that have been misfiled:</para>
-
-      <screen>&prompt.user; <userinput>query-pr -x -q -r gnats-admin</userinput>
-   52458 gnats-ad   open      serious   medium    Re: declaration clash f
-   52510 gnats-ad   open      serious   medium    Re: lots of sockets in
-   52557 gnats-ad   open      serious   medium
-   52570 gnats-ad   open      serious   medium    Jigdo maintainer update</screen>
-
-      <para>Commonly PRs like the ones shown above are misfiled for one
-	of the following reasons:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>A followup to an existing PR, sent through email, has
-	    the wrong format on its <literal>Subject:</literal>
-	    header.</para>
-	</listitem>
-
-	<listitem>
-	  <para>A submitter sent a Cc: to a mailing list and someone
-	    followed up to that post instead of the email issued by
-	    GNATS after processing.  The email to the list will not
-	    have the category/PRnumber tracking tag.  (This is why we
-	    discourage submitters from doing this exact thing.)</para>
-	</listitem>
-
-	<listitem>
-	  <para>When completing the &man.send-pr.1; template, the submitter
-	    forgot to set the category or class of the PR to a proper
-	    value.</para>
-	</listitem>
-
-	<listitem>
-	  <para>When completing the &man.send-pr.1; template, the submitter
-	    set Confidential to <literal>yes</literal>.  (Since we allow
-	    anyone to mirror GNATS via <application>rsync</application>,
-	    our PRs are public information.  Security alerts should
-	    therefore not be sent via GNATS but instead via email to
-	    the Security Team.)</para>
-	</listitem>
-
-	<listitem>
-	  <para>It is not a real PR, but some random message sent to
-	    <email>bug-followup at FreeBSD.org</email> or
-	    <email>freebsd-gnats-submit at FreeBSD.org</email>.</para>
-	</listitem>
-      </itemizedlist>
-
       <section xml:id="pr-misfiled-notpr">
 	<title>Non-Bug PRs</title>
 
@@ -920,7 +854,6 @@
 	  helps to reduce the clutter within the main categories.</para>
       </section>
     </section>
-  </section>
 
   <section xml:id="references">
     <title>Further Reading</title>