Date: Mon, 30 Jun 2014 02:47:55 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45171 - head/en_US.ISO8859-1/articles/contributing Message-ID: <201406300247.s5U2lt5f092893@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: eadler Date: Mon Jun 30 02:47:54 2014 New Revision: 45171 URL: http://svnweb.freebsd.org/changeset/doc/45171 Log: Remove additional references to send-pr Modified: head/en_US.ISO8859-1/articles/contributing/article.xml Modified: head/en_US.ISO8859-1/articles/contributing/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributing/article.xml Mon Jun 30 02:47:53 2014 (r45170) +++ head/en_US.ISO8859-1/articles/contributing/article.xml Mon Jun 30 02:47:54 2014 (r45171) @@ -251,9 +251,9 @@ other mailing lists.</para> <para>If you find a bug or are submitting a specific change, - please report it using the &man.send-pr.1; program or its - <link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">WEB-based - equivalent</link>. Try to fill-in each field of the bug + please report it using the <link + xlink:href="https://bugs.freebsd.org/submit/">bug submission form</link>. + Try to fill-in each field of the bug report. Unless they exceed 65KB, include any patches directly in the report. If the patch is suitable to be applied to the source tree put <literal>[PATCH]</literal> in the synopsis of @@ -266,17 +266,7 @@ <para>After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so - that you can update us with details about the problem by - sending mail to &a.bugfollowup;. Use the number as the - message subject, e.g. <literal>"Re: kern/3377"</literal>. - Additional information for any bug report should be submitted - this way.</para> - - <para>If you do not receive confirmation in a timely fashion (3 - days to a week, depending on your email connection) or are, - for some reason, unable to use the &man.send-pr.1; command, - then you may ask someone to file it for you by sending mail to - the &a.bugs;.</para> + that you can update us with details about the problem.</para> <para>See also <link xlink:href="&url.articles.problem-reports;/article.html">this article</link> on how to write good problem @@ -295,9 +285,8 @@ <link xlink:href="&url.books.fdp-primer;/index.html">FreeBSD Documentation Project Primer</link> for complete instructions. Send submissions and changes (even small ones - are welcome!) using &man.send-pr.1; as described in - <link linkend="contrib-general">Bug Reports and General - Commentary</link>.</para> + are welcome!) using the same method any other bug + report.</para> </sect2> <sect2> @@ -348,9 +337,8 @@ <para>Once you have a set of diffs (which you may test with the &man.patch.1; command), you should submit them for inclusion - with FreeBSD. Use the &man.send-pr.1; program as described in - <link linkend="contrib-general">Bug Reports and General - Commentary</link>. <emphasis>Do not</emphasis> just send the + with &os; as a bug report. + <emphasis>Do not</emphasis> just send the diffs to the &a.hackers; or they will get lost! We greatly appreciate your submission (this is a volunteer project!); because we are busy, we may not be able to address it @@ -368,7 +356,7 @@ <para>If your change is of a potentially sensitive nature, such as if you are unsure of copyright issues governing its further distribution then you should send it to &a.core; directly - rather than submitting it with &man.send-pr.1;. The &a.core; + rather than submitting as a bug report. The &a.core; reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this group is also <emphasis>very busy</emphasis> and so you should only send
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201406300247.s5U2lt5f092893>