Ask user to carefully examine changes when sending an upgrade. (Actually,

this is the main reason why we want them as diffs.)  Also, ask them to
explicitly state files that are added or deleted (lazy committers like me
often forget to "cvs add" or "cvs remove").

handbook/porting.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.68 1997-03-10 09:55:20 asami Exp $ -->
+<!-- $Id: porting.sgml,v 1.69 1997-03-10 11:55:17 asami Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@@ -922,8 +922,11 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 	to us (i.e., if your modified ports directory is called
 	`<tt>superedit</tt>' and the original as in our tree is
 	`<tt>superedit.bak</tt>', then send us the result of `<tt>diff
-	-ru superedit.bak superedit</tt>'.)  Please don't
-	forget to send us a message using <tt>send-pr(1)</tt>!
+	-ru superedit.bak superedit</tt>').  Please examine the output
+	to make sure all the changes make sense.  The best way to send
+	us the diff is by including it to <tt>send-pr(1)</tt>.  Please
+	mention any added or deleted files in the message, as they
+	have to be explicitly specified to CVS when doing a commit.
 
     <sect2>
       <heading>Do's and Dont's</heading>