[asterisk-commits] russell: trunk r38089 - /trunk/doc/CODING-GUIDELINES

asterisk-commits at lists.digium.com asterisk-commits at lists.digium.com
Sat Jul 22 19:50:25 MST 2006


Author: russell
Date: Sat Jul 22 21:50:25 2006
New Revision: 38089

URL: http://svn.digium.com/view/asterisk?rev=38089&view=rev
Log:
update to mention svn instead of cvs

Modified:
    trunk/doc/CODING-GUIDELINES

Modified: trunk/doc/CODING-GUIDELINES
URL: http://svn.digium.com/view/asterisk/trunk/doc/CODING-GUIDELINES?rev=38089&r1=38088&r2=38089&view=diff
==============================================================================
--- trunk/doc/CODING-GUIDELINES (original)
+++ trunk/doc/CODING-GUIDELINES Sat Jul 22 21:50:25 2006
@@ -14,17 +14,15 @@
 disclaimed to Digium or placed in the public domain. For more information
 see http://bugs.digium.com
 
-Patches should be in the form of a unified (-u) diff, made from the directory
-above the top-level Asterisk source directory. For example:
-
-- the base code you are working from is in ~/work/asterisk-base
-- the changes are in ~/work/asterisk-new
-
-~/work$ diff -urN asterisk-base asterisk-new
-
-If you are changing within a fresh CVS/SVN repository, you can create
-a patch with
-$ cvs diff -urN <mycodefile>.c
+Patches should be in the form of a unified (-u) diff, made from a checkout
+from subversion.
+
+/usr/src/asterisk$ svn diff > mypatch
+
+If you would like to only include changes to certain files in the patch, you
+can list them in the "svn diff" command:
+
+/usr/src/asterisk$ svn diff somefile.c someotherfile.c > mypatch
 
 * General rules
 ---------------



More information about the asterisk-commits mailing list