diff options
| author | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2005-11-30 03:37:37 +0000 |
|---|---|---|
| committer | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2005-11-30 03:37:37 +0000 |
| commit | 3d3a6cffa0e7f4fbe94b7a3af647aa0a3f26c9b0 (patch) | |
| tree | 900494600f2c50e4ad554b3da4dc810caff81e33 /doc/CODING-GUIDELINES | |
| parent | 0a2070a04d7894b0b09ece1cc14c5b534b232f4f (diff) | |
remove remaining CVS references
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.2@7226 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc/CODING-GUIDELINES')
| -rw-r--r-- | doc/CODING-GUIDELINES | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES index 3d296a75c..c3c62bfdd 100644 --- a/doc/CODING-GUIDELINES +++ b/doc/CODING-GUIDELINES @@ -22,9 +22,9 @@ above the top-level Asterisk source directory. For example: ~/work$ diff -urN asterisk-base asterisk-new -If you are changing within a fresh CVS/SVN repository, you can create +If you are changing within a fresh SVN working copy, you can create a patch with -$ cvs diff -urN <mycodefile>.c +$ svn diff <mycodefile>.c * General rules --------------- @@ -464,7 +464,7 @@ Before submitting a patch, *read* the actual patch file to be sure that all the changes you expect to be there are, and that there are no surprising changes you did not expect. During your development, that part of Asterisk may have changed, so make sure you compare with the -latest CVS. +latest SVN. - Listen to advice If you are asked to make changes to your patch, there is a good chance |