jon             Sun Feb 18 09:47:44 2001 EDT

  Modified files:              
    /php4/pear  CODING_STANDARDS 
  Log:
  Go back to listing the copyright years explicitly (instead of using a
  range).
  
  
Index: php4/pear/CODING_STANDARDS
diff -u php4/pear/CODING_STANDARDS:1.4 php4/pear/CODING_STANDARDS:1.5
--- php4/pear/CODING_STANDARDS:1.4      Tue Jan  9 09:42:40 2001
+++ php4/pear/CODING_STANDARDS  Sun Feb 18 09:47:43 2001
@@ -2,7 +2,7 @@
 || PEAR Coding Standards                                                 ||
 ===========================================================================
 
-$Id: CODING_STANDARDS,v 1.4 2001/01/09 17:42:40 jon Exp $
+$Id: CODING_STANDARDS,v 1.5 2001/02/18 17:47:43 jon Exp $
 
 -------------
 [1] Indenting
@@ -174,7 +174,7 @@
 // +----------------------------------------------------------------------+
 // | PHP version 4.0                                                      |
 // +----------------------------------------------------------------------+
-// | Copyright (c) 1997-2001 The PHP Group                                |
+// | Copyright (c) 1997, 1998, 1999, 2000, 2001 The PHP Group             |
 // +----------------------------------------------------------------------+
 // | This source file is subject to version 2.0 of the PHP license,       |
 // | that is bundled with this package in the file LICENSE, and is        |
@@ -188,7 +188,7 @@
 // |          Your Name <[EMAIL PROTECTED]>                                 |
 // +----------------------------------------------------------------------+
 //
-// $Id: CODING_STANDARDS,v 1.4 2001/01/09 17:42:40 jon Exp $
+// $Id: CODING_STANDARDS,v 1.5 2001/02/18 17:47:43 jon Exp $
 
 There's no hard rule to determine when a new code contributer should be
 added to the list of authors for a given source file.  In general, their



-- 
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to