From nobody@FreeBSD.org  Fri Feb 29 02:15:41 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 529BD1065674
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 29 Feb 2008 02:15:41 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 3D11E8FC14
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 29 Feb 2008 02:15:41 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m1T2CpUr007674
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 29 Feb 2008 02:12:51 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.2/8.14.1/Submit) id m1T2Cpuw007673;
	Fri, 29 Feb 2008 02:12:51 GMT
	(envelope-from nobody)
Message-Id: <200802290212.m1T2Cpuw007673@www.freebsd.org>
Date: Fri, 29 Feb 2008 02:12:51 GMT
From: Chess Griffin <chess@chessgriffin.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: [patch] edits to books/porters-handbook
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         121197
>Category:       docs
>Synopsis:       [patch] edits to books/porters-handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    tabthorpe
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 29 02:20:01 UTC 2008
>Closed-Date:    Tue Jan 27 16:07:04 UTC 2009
>Last-Modified:  Tue Jan 27 16:10:03 UTC 2009
>Originator:     Chess Griffin
>Release:        7.0-RELEASE
>Organization:
>Environment:
FreeBSD bsdbob.localdomain 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Mon Feb 25 19:09:06 EST 2008     chess@bsdbob.localdomain:/usr/obj/usr/src/sys/CHESS  i38
>Description:
Attached are some minor edits plus one small addition to the Porter's Handbook.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- book.sgml.orig	2008-02-28 19:06:47.000000000 -0500
+++ book.sgml	2008-02-28 21:09:37.000000000 -0500
@@ -2465,10 +2465,10 @@
 	  hereon.</para>
 
 	<para>A little background first.  OpenBSD has a neat feature
-	  inside both <makevar>DISTFILES</makevar> and
-	  <makevar>PATCHFILES</makevar> variables, both files and
-	  patches can be postfixed with <literal>:n</literal>
-	  identifiers where <literal>n</literal> both can be
+	  inside the <makevar>DISTFILES</makevar> and
+	  <makevar>PATCHFILES</makevar> variables which allows files
+	  and patches to be postfixed with <literal>:n</literal>
+	  identifiers, where <literal>n</literal> both can be
 	  <literal>[0-9]</literal> and denote a group designation.
 	  For example:</para>
 
@@ -2489,7 +2489,7 @@
 	  as hell where <filename>beta</filename> is carried by all
 	  sites in <makevar>MASTER_SITES</makevar>, and
 	  <filename>alpha</filename> can only be found in the 20th
-	  site.  It would be such a waste to check all of them if
+	  site.  It would be such a waste to check all of them if the
 	  maintainer knew this beforehand, would it not?  Not a good
 	  start for that lovely weekend!</para>
 
@@ -3174,24 +3174,25 @@
 	  challenge for port maintainers</ulink> section.</para>
 
 	<para>Changes to the port will be sent to the maintainer of
-	  a port for a review and an approval before being committed.
-	  If the maintainer does not respond to an update
-	  request after two weeks (excluding major public
-	  holidays), then that is considered a maintainer timeout, and the
-	  update may be made without explicit maintainer approval.  If the
-	  maintainer does not respond within three months, then that
-	  maintainer is considered absent without leave, and can be
-	  replaced as the maintainer of the particular port in question.
-	  Exceptions to this are anything maintained by the &a.portmgr;, or
-	  the &a.security-officer;.  No unauthorized commits may ever be
-	  made to ports maintained by those groups.</para>
+	  a port for review and approval before being committed.  If
+	  the maintainer does not respond to an update request after
+	  two weeks (excluding major public holidays), then that is
+	  considered a maintainer timeout, and the update may be made
+	  without explicit maintainer approval.  If the maintainer
+	  does not respond within three months, then that maintainer
+	  is considered absent without leave, and can be replaced as
+	  the maintainer of the particular port in question.
+	  Exceptions to this are anything maintained by the
+	  &a.portmgr;, or the &a.security-officer;.  No unauthorized
+	  commits may ever be made to ports maintained by those
+	  groups.</para>
 
 	<para>We reserve the right to modify the maintainer's submission
 	  to better match existing policies and style of the Ports
 	  Collection without explicit blessing from the submitter.
 	  Also, large infrastructural changes can result in
-	  a port being modified without maintainer's consent.
-	  This kind of changes will never affect the port's
+	  a port being modified without the maintainer's consent.
+	  These kinds of changes will never affect the port's
 	  functionality.</para>
 
 	<para>The &a.portmgr; reserves the right to revoke or override
@@ -4180,14 +4181,16 @@
 	  under <makevar>PREFIX</makevar>.</para>
 
 	<para>Two macros exists for this situation.  The advantage of using
-	  these macros instead of <command>cp</command> is that they guarantee
-	  proper file ownership and permissions on target files.  First macro,
-	  <makevar>COPYTREE_BIN</makevar>, will set all the installed files to
-	  be executable, thus being suitable for installing into
-	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The second
-	  macro, <makevar>COPYTREE_SHARE</makevar>, does not set executable
-	  permissions on files, and is therefore suitable for installing files
-	  under <filename><makevar>PREFIX</makevar>/share</filename>
+	  these macros instead of <command>cp</command> is that they
+	  guarantee proper file ownership and permissions on target
+	  files.  The first macro, <makevar>COPYTREE_BIN</makevar>,
+	  will set all the installed files to be executable, thus
+	  being suitable for installing into
+	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The
+	  second macro, <makevar>COPYTREE_SHARE</makevar>, does not
+	  set executable permissions on files, and is therefore
+	  suitable for installing files under
+	  <filename><makevar>PREFIX</makevar>/share</filename>
 	  target.</para>
 
 	<programlisting>post-install:
@@ -8591,6 +8594,12 @@
       <para>The packing list still has to be tidied up by hand as
 	stated above.</para>
 
+      <para>Another tool that might be used to create a
+	<filename>pkg-plist</filename> as a starting point is
+	<application>ports-mgmt/genplist</application>.  As with any
+	automated tool, the resulting <filename>pkg-plist</filename>
+	should be checked and manually edited as needed.</para>
+
     </sect1>
 
     </chapter>
@@ -11809,7 +11818,7 @@
 		  <row>
 		    <entry>7.0-CURRENT after
 		      RFC 3678 API support added to the IPv4 stack.
-		      Legacy RFC 1724 behaviour of the IP_MULTICAST_IF
+		      Legacy RFC 1724 behavior of the IP_MULTICAST_IF
 		      ioctl has now been removed; 0.0.0.0/8 may no longer
 		      be used to specify an interface index.
 		      struct ipmreqn should be used instead.</entry>


>Release-Note:
>Audit-Trail:

From: Pav Lucistnik <pav@FreeBSD.org>
To: bug-followup@FreeBSD.org, chess@chessgriffin.com
Cc:  
Subject: Re: docs/121197: [patch] edits to books/porters-handbook
Date: Fri, 29 Feb 2008 09:57:44 +0100

 Hi Chess,
 can you confirm that your patch contains only English-related, but not
 meaning altering changes (except the one before last chunk, which
 obviously adds a new content) ?
 
 Also, can you undo the rewrapping of chunks 3174 and 4180, so the actual
 changes are more obvious from the diff? We never rewrap whole
 paragraphs, because it makes the work of translators harder.
 
 -- 
 Pav Lucistnik <pav@oook.cz>
               <pav@FreeBSD.org>
 
 94 outdated ports on the box,
 94 outdated ports.
 Portupgrade one, an hour 'til done,
 82 outdated ports on the box.

From: Chess Griffin <chess@chessgriffin.com>
To: bug-followup@FreeBSD.org, chess@chessgriffin.com
Cc:  
Subject: Re: docs/121197: [patch] edits to books/porters-handbook
Date: Fri, 29 Feb 2008 09:30:04 -0500

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enig72A61CB56C75BDF0A54BF848
 Content-Type: multipart/mixed;
  boundary="------------050801060003020905080601"
 
 This is a multi-part message in MIME format.
 --------------050801060003020905080601
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: quoted-printable
 
 Pav,
 
 Thanks for the comments.  Yes, other than the two lines of new content=20
 added at line 8591 regarding genplist, the other changes are just minor=20
 grammatical edits.
 
 I have attached a new patch without the rewrapping.  Sorry about that -- =
 
 just habit, I guess.  :-)
 
 
 --=20
 Chess Griffin
 GPG Key:  0x0C7558C3
 http://www.chessgriffin.com
 
 --------------050801060003020905080601
 Content-Type: text/plain;
  name="porters.diff"
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline;
  filename="porters.diff"
 
 --- book.sgml.orig	2008-02-28 19:06:47.000000000 -0500
 +++ book.sgml	2008-02-29 09:12:24.000000000 -0500
 @@ -2465,10 +2465,10 @@
  	  hereon.</para>
 =20
  	<para>A little background first.  OpenBSD has a neat feature
 -	  inside both <makevar>DISTFILES</makevar> and
 -	  <makevar>PATCHFILES</makevar> variables, both files and
 -	  patches can be postfixed with <literal>:n</literal>
 -	  identifiers where <literal>n</literal> both can be
 +	  inside the <makevar>DISTFILES</makevar> and
 +	  <makevar>PATCHFILES</makevar> variables which allows files and
 +	  patches to be postfixed with <literal>:n</literal>
 +	  identifiers, where <literal>n</literal> both can be
  	  <literal>[0-9]</literal> and denote a group designation.
  	  For example:</para>
 =20
 @@ -2489,7 +2489,7 @@
  	  as hell where <filename>beta</filename> is carried by all
  	  sites in <makevar>MASTER_SITES</makevar>, and
  	  <filename>alpha</filename> can only be found in the 20th
 -	  site.  It would be such a waste to check all of them if
 +	  site.  It would be such a waste to check all of them if the
  	  maintainer knew this beforehand, would it not?  Not a good
  	  start for that lovely weekend!</para>
 =20
 @@ -3174,7 +3174,7 @@
  	  challenge for port maintainers</ulink> section.</para>
 =20
  	<para>Changes to the port will be sent to the maintainer of
 -	  a port for a review and an approval before being committed.
 +	  a port for review and approval before being committed.
  	  If the maintainer does not respond to an update
  	  request after two weeks (excluding major public
  	  holidays), then that is considered a maintainer timeout, and the
 @@ -3191,7 +3191,7 @@
  	  Collection without explicit blessing from the submitter.
  	  Also, large infrastructural changes can result in
  	  a port being modified without maintainer's consent.
 -	  This kind of changes will never affect the port's
 +	  These kinds of changes will never affect the port's
  	  functionality.</para>
 =20
  	<para>The &a.portmgr; reserves the right to revoke or override
 @@ -4181,7 +4181,7 @@
 =20
  	<para>Two macros exists for this situation.  The advantage of using
  	  these macros instead of <command>cp</command> is that they guarantee
 -	  proper file ownership and permissions on target files.  First macro,
 +	  proper file ownership and permissions on target files.  The first mac=
 ro,
  	  <makevar>COPYTREE_BIN</makevar>, will set all the installed files to
  	  be executable, thus being suitable for installing into
  	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The second
 @@ -8591,6 +8591,12 @@
        <para>The packing list still has to be tidied up by hand as
  	stated above.</para>
 =20
 +      <para>Another tool that might be used to create an initial
 +	<filename>pkg-plist</filename> is <filename
 +	role=3D"package">ports-mgmt/genplist</filename>.  As with any
 +	automated tool, the resulting <filename>pkg-plist</filename>
 +	should be checked and manually edited as needed.</para>
 +
      </sect1>
 =20
      </chapter>
 @@ -11809,7 +11815,7 @@
  		  <row>
  		    <entry>7.0-CURRENT after
  		      RFC 3678 API support added to the IPv4 stack.
 -		      Legacy RFC 1724 behaviour of the IP_MULTICAST_IF
 +		      Legacy RFC 1724 behavior of the IP_MULTICAST_IF
  		      ioctl has now been removed; 0.0.0.0/8 may no longer
  		      be used to specify an interface index.
  		      struct ipmreqn should be used instead.</entry>
 
 --------------050801060003020905080601--
 
 --------------enig72A61CB56C75BDF0A54BF848
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.2 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iD8DBQFHyBbvKzd9mAx1WMMRAkx2AJ943mENHi7RHKGeh3wNs24nRKXciACeL8qN
 +0DECAdxvfLQP6RgFC5M9Ek=
 =JLbg
 -----END PGP SIGNATURE-----
 
 --------------enig72A61CB56C75BDF0A54BF848--

From: Chess Griffin <chess@chessgriffin.com>
To: bug-followup@FreeBSD.org, chess@chessgriffin.com
Cc:  
Subject: Re: docs/121197: [patch] edits to books/porters-handbook
Date: Fri, 29 Feb 2008 10:18:07 -0500

 --OgqxwSJOaUobr8KG
 Content-Type: text/plain; charset=iso-8859-1
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Wow, that attachment came through pretty ugly.  Here it is again:
 
 
 --- book.sgml.orig	2008-02-28 19:06:47.000000000 -0500
 +++ book.sgml	2008-02-29 10:17:08.000000000 -0500
 @@ -2465,10 +2465,10 @@
  	  hereon.</para>
 =20
  	<para>A little background first.  OpenBSD has a neat feature
 -	  inside both <makevar>DISTFILES</makevar> and
 -	  <makevar>PATCHFILES</makevar> variables, both files and
 -	  patches can be postfixed with <literal>:n</literal>
 -	  identifiers where <literal>n</literal> both can be
 +	  inside the <makevar>DISTFILES</makevar> and
 +	  <makevar>PATCHFILES</makevar> variables which allows files and
 +	  patches to be postfixed with <literal>:n</literal>
 +	  identifiers, where <literal>n</literal> both can be
  	  <literal>[0-9]</literal> and denote a group designation.
  	  For example:</para>
 =20
 @@ -2489,7 +2489,7 @@
  	  as hell where <filename>beta</filename> is carried by all
  	  sites in <makevar>MASTER_SITES</makevar>, and
  	  <filename>alpha</filename> can only be found in the 20th
 -	  site.  It would be such a waste to check all of them if
 +	  site.  It would be such a waste to check all of them if the
  	  maintainer knew this beforehand, would it not?  Not a good
  	  start for that lovely weekend!</para>
 =20
 @@ -3174,7 +3174,7 @@
  	  challenge for port maintainers</ulink> section.</para>
 =20
  	<para>Changes to the port will be sent to the maintainer of
 -	  a port for a review and an approval before being committed.
 +	  a port for review and approval before being committed.
  	  If the maintainer does not respond to an update
  	  request after two weeks (excluding major public
  	  holidays), then that is considered a maintainer timeout, and the
 @@ -3191,7 +3191,7 @@
  	  Collection without explicit blessing from the submitter.
  	  Also, large infrastructural changes can result in
  	  a port being modified without maintainer's consent.
 -	  This kind of changes will never affect the port's
 +	  These kinds of changes will never affect the port's
  	  functionality.</para>
 =20
  	<para>The &a.portmgr; reserves the right to revoke or override
 @@ -4181,7 +4181,7 @@
 =20
  	<para>Two macros exists for this situation.  The advantage of using
  	  these macros instead of <command>cp</command> is that they guarantee
 -	  proper file ownership and permissions on target files.  First macro,
 +	  proper file ownership and permissions on target files.  The first macro,
  	  <makevar>COPYTREE_BIN</makevar>, will set all the installed files to
  	  be executable, thus being suitable for installing into
  	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The second
 @@ -8591,6 +8591,12 @@
        <para>The packing list still has to be tidied up by hand as
  	stated above.</para>
 =20
 +      <para>Another tool that might be used to create an initial
 +        <filename>pkg-plist</filename> is <filename
 +        role=3D"package">ports-mgmt/genplist</filename>.  As with any
 +        automated tool, the resulting <filename>pkg-plist</filename>
 +        should be checked and manually edited as needed.</para>
 +
      </sect1>
 =20
      </chapter>
 @@ -11809,7 +11815,7 @@
  		  <row>
  		    <entry>7.0-CURRENT after
  		      RFC 3678 API support added to the IPv4 stack.
 -		      Legacy RFC 1724 behaviour of the IP_MULTICAST_IF
 +		      Legacy RFC 1724 behavior of the IP_MULTICAST_IF
  		      ioctl has now been removed; 0.0.0.0/8 may no longer
  		      be used to specify an interface index.
  		      struct ipmreqn should be used instead.</entry>
 
 --=20
 Chess Griffin
 GPG Public Key:  0x0C7558C3
 http://www.chessgriffin.com
 
 --OgqxwSJOaUobr8KG
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.4 (FreeBSD)
 
 iD8DBQFHyCIvKzd9mAx1WMMRAkbMAJ49jie6QxfLLG6dMCDTk3HxaCOKMQCff24q
 nD7nxS1hoPMUerbe/fQO4N8=
 =E0Rd
 -----END PGP SIGNATURE-----
 
 --OgqxwSJOaUobr8KG--

From: Chess Griffin <chess@chessgriffin.com>
To: bug-followup@FreeBSD.org, chess@chessgriffin.com
Cc:  
Subject: Re: docs/121197: [patch] edits to books/porters-handbook
Date: Fri, 29 Feb 2008 18:59:41 -0500

 --huq684BweRXVnRxX
 Content-Type: text/plain; charset=iso-8859-1
 Content-Disposition: inline
 
 One more edit suggested me by someone off-list.  Thanks.
 
 -- 
 Chess Griffin
 GPG Public Key:  0x0C7558C3
 http://www.chessgriffin.com
 
 --huq684BweRXVnRxX
 Content-Type: text/x-diff; charset=iso-8859-1
 Content-Disposition: attachment; filename="porterspatch.diff"
 
 --- book.sgml.orig	2008-02-28 19:06:47.000000000 -0500
 +++ book.sgml	2008-02-29 18:57:03.000000000 -0500
 @@ -2465,10 +2465,10 @@
  	  hereon.</para>
  
  	<para>A little background first.  OpenBSD has a neat feature
 -	  inside both <makevar>DISTFILES</makevar> and
 -	  <makevar>PATCHFILES</makevar> variables, both files and
 -	  patches can be postfixed with <literal>:n</literal>
 -	  identifiers where <literal>n</literal> both can be
 +	  inside the <makevar>DISTFILES</makevar> and
 +	  <makevar>PATCHFILES</makevar> variables which allows files and
 +	  patches to be postfixed with <literal>:n</literal>
 +	  identifiers, where <literal>n</literal> both can be
  	  <literal>[0-9]</literal> and denote a group designation.
  	  For example:</para>
  
 @@ -2489,7 +2489,7 @@
  	  as hell where <filename>beta</filename> is carried by all
  	  sites in <makevar>MASTER_SITES</makevar>, and
  	  <filename>alpha</filename> can only be found in the 20th
 -	  site.  It would be such a waste to check all of them if
 +	  site.  It would be such a waste to check all of them if the
  	  maintainer knew this beforehand, would it not?  Not a good
  	  start for that lovely weekend!</para>
  
 @@ -3174,7 +3174,7 @@
  	  challenge for port maintainers</ulink> section.</para>
  
  	<para>Changes to the port will be sent to the maintainer of
 -	  a port for a review and an approval before being committed.
 +	  a port for review and approval before being committed.
  	  If the maintainer does not respond to an update
  	  request after two weeks (excluding major public
  	  holidays), then that is considered a maintainer timeout, and the
 @@ -3191,7 +3191,7 @@
  	  Collection without explicit blessing from the submitter.
  	  Also, large infrastructural changes can result in
  	  a port being modified without maintainer's consent.
 -	  This kind of changes will never affect the port's
 +	  These kinds of changes will never affect the port's
  	  functionality.</para>
  
  	<para>The &a.portmgr; reserves the right to revoke or override
 @@ -4179,9 +4179,9 @@
  	  directory tree from <makevar>WRKSRC</makevar> to a target directory
  	  under <makevar>PREFIX</makevar>.</para>
  
 -	<para>Two macros exists for this situation.  The advantage of using
 +	<para>Two macros exist for this situation.  The advantage of using
  	  these macros instead of <command>cp</command> is that they guarantee
 -	  proper file ownership and permissions on target files.  First macro,
 +	  proper file ownership and permissions on target files.  The first macro,
  	  <makevar>COPYTREE_BIN</makevar>, will set all the installed files to
  	  be executable, thus being suitable for installing into
  	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The second
 @@ -8591,6 +8591,12 @@
        <para>The packing list still has to be tidied up by hand as
  	stated above.</para>
  
 +      <para>Another tool that might be used to create an initial
 +        <filename>pkg-plist</filename> is <filename
 +        role="package">ports-mgmt/genplist</filename>.  As with any
 +        automated tool, the resulting <filename>pkg-plist</filename>
 +        should be checked and manually edited as needed.</para>
 +
      </sect1>
  
      </chapter>
 @@ -11809,7 +11815,7 @@
  		  <row>
  		    <entry>7.0-CURRENT after
  		      RFC 3678 API support added to the IPv4 stack.
 -		      Legacy RFC 1724 behaviour of the IP_MULTICAST_IF
 +		      Legacy RFC 1724 behavior of the IP_MULTICAST_IF
  		      ioctl has now been removed; 0.0.0.0/8 may no longer
  		      be used to specify an interface index.
  		      struct ipmreqn should be used instead.</entry>
 
 --huq684BweRXVnRxX--
Responsible-Changed-From-To: freebsd-doc->tabthorpe 
Responsible-Changed-By: tabthorpe 
Responsible-Changed-When: Tue Jan 27 03:36:38 UTC 2009 
Responsible-Changed-Why:  
I'll take it. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=121197 

From: Thomas Abthorpe <tabthorpe@freebsd.org>
To: bug-followup@freebsd.org, chess@chessgriffin.com
Cc:  
Subject: Re: docs/121197: [patch] edits to books/porters-handbook
Date: Tue, 27 Jan 2009 00:11:27 -0500

 --nextPart10963684.EUdUWYUHoC
 Content-Type: multipart/mixed;
   boundary="Boundary-01=_CepfJuRv4dpHZHf"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline
 
 --Boundary-01=_CepfJuRv4dpHZHf
 Content-Type: text/plain;
   charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline
 
 Please find attached a unified patch incorporating the combined efforts of =
 the=20
 author, while (hopefully) respecting the requisite whitespace for translato=
 r=20
 efforts.
 
 Thomas
 
 =2D-=20
 Thomas Abthorpe		| FreeBSD Committer
 tabthorpe@FreeBSD.org	| http://people.freebsd.org/~tabthorpe
 
 --Boundary-01=_CepfJuRv4dpHZHf
 Content-Type: text/x-diff;
   charset="iso 8859-15";
   name="ph-book.patch"
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: attachment;
 	filename="ph-book.patch"
 
 Index: book.sgml
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
 retrieving revision 1.970
 diff -u -r1.970 book.sgml
 =2D-- book.sgml	21 Jan 2009 13:05:36 -0000	1.970
 +++ book.sgml	27 Jan 2009 05:04:23 -0000
 @@ -2412,10 +2412,10 @@
  	  hereon.</para>
 =20
  	<para>A little background first.  OpenBSD has a neat feature
 =2D	  inside both <makevar>DISTFILES</makevar> and
 =2D	  <makevar>PATCHFILES</makevar> variables, both files and
 =2D	  patches can be postfixed with <literal>:n</literal>
 =2D	  identifiers where <literal>n</literal> both can be
 +	  inside the <makevar>DISTFILES</makevar> and
 +	  <makevar>PATCHFILES</makevar> variables which allows files and
 +	  patches to be postfixed with <literal>:n</literal>
 +	  identifiers, where <literal>n</literal> both can be
  	  <literal>[0-9]</literal> and denote a group designation.
  	  For example:</para>
 =20
 @@ -2436,7 +2436,7 @@
  	  as hell where <filename>beta</filename> is carried by all
  	  sites in <makevar>MASTER_SITES</makevar>, and
  	  <filename>alpha</filename> can only be found in the 20th
 =2D	  site.  It would be such a waste to check all of them if
 +	  site.  It would be such a waste to check all of them if the
  	  maintainer knew this beforehand, would it not?  Not a good
  	  start for that lovely weekend!</para>
 =20
 @@ -3121,7 +3121,7 @@
  	  challenge for port maintainers</ulink> section.</para>
 =20
  	<para>Changes to the port will be sent to the maintainer of
 =2D	  a port for a review and an approval before being committed.
 +	  a port for review and approval before being committed.
  	  If the maintainer does not respond to an update
  	  request after two weeks (excluding major public
  	  holidays), then that is considered a maintainer timeout, and the
 @@ -3137,8 +3137,8 @@
  	  to better match existing policies and style of the Ports
  	  Collection without explicit blessing from the submitter.
  	  Also, large infrastructural changes can result in
 =2D	  a port being modified without maintainer's consent.
 =2D	  This kind of changes will never affect the port's
 +	  a port being modified without the maintainer's consent.
 +	  These kinds of changes will never affect the port's
  	  functionality.</para>
 =20
  	<para>The &a.portmgr; reserves the right to revoke or override
 @@ -4090,7 +4090,7 @@
 =20
  	<para>Two macros exists for this situation.  The advantage of using
  	  these macros instead of <command>cp</command> is that they guarantee
 =2D	  proper file ownership and permissions on target files.  First macro,
 +	  proper file ownership and permissions on target files.  The first macro,
  	  <makevar>COPYTREE_BIN</makevar>, will set all the installed files to
  	  be executable, thus being suitable for installing into
  	  <filename><makevar>PREFIX</makevar>/bin</filename>.  The second
 @@ -8645,6 +8645,11 @@
        <para>The packing list still has to be tidied up by hand as
  	stated above.</para>
 =20
 +      <para>Another tool that might be used to create an initial
 +	<filename>pkg-plist</filename> is <filename
 +	role=3D"package">ports-mgmt/genplist</filename>. As with any
 +	automated tool, the resulting <filename>pkg-plist</filename>
 +	should be checked and manually edited as needed.</para>
      </sect1>
 =20
      </chapter>
 @@ -11882,7 +11887,7 @@
  		  <row>
  		    <entry>7.0-CURRENT after
  		      RFC 3678 API support added to the IPv4 stack.
 =2D		      Legacy RFC 1724 behaviour of the IP_MULTICAST_IF
 +		      Legacy RFC 1724 behavior of the IP_MULTICAST_IF
  		      ioctl has now been removed; 0.0.0.0/8 may no longer
  		      be used to specify an interface index.
  		      struct ipmreqn should be used instead.</entry>
 
 --Boundary-01=_CepfJuRv4dpHZHf--
 
 --nextPart10963684.EUdUWYUHoC
 Content-Type: application/pgp-signature; name=signature.asc 
 Content-Description: This is a digitally signed message part.
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.10 (FreeBSD)
 
 iEYEABECAAYFAkl+l4IACgkQ5Gm/jNBp8qC+PQCfUIi0Gt5ObM91sM2u33JawKul
 /KoAoIP+WGwF1mtVUTXj9kkryg234O3B
 =IEOq
 -----END PGP SIGNATURE-----
 
 --nextPart10963684.EUdUWYUHoC--
State-Changed-From-To: open->closed 
State-Changed-By: tabthorpe 
State-Changed-When: Tue Jan 27 16:07:04 UTC 2009 
State-Changed-Why:  
Committed. Thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=121197 

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/121197: commit references a PR
Date: Tue, 27 Jan 2009 16:05:53 +0000 (UTC)

 tabthorpe    2009-01-27 16:05:37 UTC
 
   FreeBSD doc repository (ports committer)
 
   Modified files:
     en_US.ISO8859-1/books/porters-handbook book.sgml 
   Log:
   - Clean up some grammar
   - Document ports-mgmt/genplist
   
   PR:             docs/121197
   Submitted by:   Chess Griffin <chess chessgriffin.com>
   Reviewed by:    pav
   Approved by:    trhodes
   
   Revision  Changes    Path
   1.971     +15 -10    doc/en_US.ISO8859-1/books/porters-handbook/book.sgml
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
>Unformatted:
