os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Mention that [PATCH] in the synopsis of a PR could indicate that the

Browse source 
PR includes a patch suitable for committing.  I don't think this is
the best place to put something like this, but it's better than
nothing.

Submitted by:	pavalos@theshell.com
This commit is contained in:
Dima Dorfman 2001-08-11 20:15:56 +00:00
parent 72027ff066
commit 5629b58727
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10307
2 changed files with 12 additions and 6 deletions
en_US.ISO8859-1
articles/contributing
article.sgml
books/handbook/contrib
chapter.sgml

9
en_US.ISO8859-1/articles/contributing/article.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.466 2001/08/09 23:42:30 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.467 2001/08/10 22:58:11 chern Exp $
-->
<chapter id="contrib">
@ -192,6 +192,8 @@
url="http://www.FreeBSD.org/send-pr.html">WEB-based
equivalent</ulink>. 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 the report.
When including patches, <emphasis>do not</emphasis> use cut-and-paste
because cut-and-paste turns tabs into spaces and makes them unusable.
Consider compressing patches and using &man.uuencode.1; if they exceed
@ -268,8 +270,9 @@
<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 immediately, but it will remain in the pr database until we
do.</para>
address it immediately, but it will remain in the PR database until we
do. Indicate your submission by including <literal>[PATCH]</literal>
in the synopsis of the report.</para>
<indexterm>
<primary><command>uuencode</command></primary>

9
en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.466 2001/08/09 23:42:30 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.467 2001/08/10 22:58:11 chern Exp $
-->
<chapter id="contrib">
@ -192,6 +192,8 @@
url="http://www.FreeBSD.org/send-pr.html">WEB-based
equivalent</ulink>. 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 the report.
When including patches, <emphasis>do not</emphasis> use cut-and-paste
because cut-and-paste turns tabs into spaces and makes them unusable.
Consider compressing patches and using &man.uuencode.1; if they exceed
@ -268,8 +270,9 @@
<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 immediately, but it will remain in the pr database until we
do.</para>
address it immediately, but it will remain in the PR database until we
do. Indicate your submission by including <literal>[PATCH]</literal>
in the synopsis of the report.</para>
<indexterm>
<primary><command>uuencode</command></primary>