From owner-svn-doc-all@FreeBSD.ORG Mon Jun 30 02:47:55 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CB25CC1; Mon, 30 Jun 2014 02:47:55 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 497A620C6; Mon, 30 Jun 2014 02:47:55 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s5U2lt6C092894; Mon, 30 Jun 2014 02:47:55 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s5U2lt5f092893; Mon, 30 Jun 2014 02:47:55 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201406300247.s5U2lt5f092893@svn.freebsd.org> From: Eitan Adler Date: Mon, 30 Jun 2014 02:47:55 +0000 (UTC) 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 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2014 02:47:55 -0000 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. If you find a bug or are submitting a specific change, - please report it using the &man.send-pr.1; program or its - WEB-based - equivalent. Try to fill-in each field of the bug + please report it using the bug submission form. + 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 [PATCH] in the synopsis of @@ -266,17 +266,7 @@ 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. "Re: kern/3377". - Additional information for any bug report should be submitted - this way. - - 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;. + that you can update us with details about the problem. See also this article on how to write good problem @@ -295,9 +285,8 @@ FreeBSD Documentation Project Primer for complete instructions. Send submissions and changes (even small ones - are welcome!) using &man.send-pr.1; as described in - Bug Reports and General - Commentary. + are welcome!) using the same method any other bug + report. @@ -348,9 +337,8 @@ 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 - Bug Reports and General - Commentary. Do not just send the + with &os; as a bug report. + Do not 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 @@ 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 very busy and so you should only send