Add <note>, that PR's with a synopsis like
New port: xfoo, a foobar program or Update port: astro/xfoo - unbreak and update to 1.3.4 helps the committers a lot.
This commit is contained in:
parent
5455291c58
commit
785301f258
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7607
2 changed files with 26 additions and 2 deletions
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml,v 1.112 2000/07/09 02:00:25 dannyboy Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml,v 1.113 2000/07/11 17:15:07 obrien Exp $
|
||||
-->
|
||||
|
||||
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
|
||||
|
@ -357,6 +357,18 @@ lib/X11/oneko/mouse.xpm
|
|||
“Additional FreeBSD contributors” in the FreeBSD
|
||||
Handbook and other files. Isn't that great?!? <!-- smiley
|
||||
-->:-)</para>
|
||||
|
||||
<note>
|
||||
<para>You can make our work a lot easier, if you use a good
|
||||
description in the synopsis of the problem report.
|
||||
We prefer something like
|
||||
“New port: <short description of the port>” for
|
||||
new ports and
|
||||
“Update port: <category>/<port> <short description
|
||||
of the update>” for port updates.
|
||||
If you stick to this scheme, the chance that one takes a look at
|
||||
your PR soon is much bigger.</para>
|
||||
</note>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml,v 1.112 2000/07/09 02:00:25 dannyboy Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/porters-handbook/book.sgml,v 1.113 2000/07/11 17:15:07 obrien Exp $
|
||||
-->
|
||||
|
||||
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
|
||||
|
@ -357,6 +357,18 @@ lib/X11/oneko/mouse.xpm
|
|||
“Additional FreeBSD contributors” in the FreeBSD
|
||||
Handbook and other files. Isn't that great?!? <!-- smiley
|
||||
-->:-)</para>
|
||||
|
||||
<note>
|
||||
<para>You can make our work a lot easier, if you use a good
|
||||
description in the synopsis of the problem report.
|
||||
We prefer something like
|
||||
“New port: <short description of the port>” for
|
||||
new ports and
|
||||
“Update port: <category>/<port> <short description
|
||||
of the update>” for port updates.
|
||||
If you stick to this scheme, the chance that one takes a look at
|
||||
your PR soon is much bigger.</para>
|
||||
</note>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
|
Loading…
Reference in a new issue