Author: turnstep
Date: Mon Mar 12 13:45:57 2007
New Revision: 9240

Modified:
   DBD-Pg/trunk/README.dev

Log:
Quick updates, change a few things from cvs to svn.


Modified: DBD-Pg/trunk/README.dev
==============================================================================
--- DBD-Pg/trunk/README.dev     (original)
+++ DBD-Pg/trunk/README.dev     Mon Mar 12 13:45:57 2007
@@ -290,7 +290,7 @@
 
 etc...
 
-It's also a good idea to test the current cvs version of pg in your tests: 
this can detect 
+It's also a good idea to test the current cvs version of Postgres in your 
tests: this can detect 
 changes nice and early.
 
 In addition to different versions of Postgres, it's a good idea to test a few 
versions of 
@@ -503,11 +503,11 @@
 
 * Created a standard header for the file, with a (dollar sign)Id(dollar sign)
 
-* Added it to cvs via 'cvs add filename' and 'cvs commit filename'
+* Added it to subversion via 'svn add filename' and 'svn commit filename'
 
 * Added it to the MANIFEST file
 
-* Added to Makefile.PL if needed, to make sure all build dependencies are met
+* Added it to Makefile.PL if needed, to make sure all build dependencies are 
met
 
 * Updated/created necessary tests for it
 
@@ -532,7 +532,7 @@
 
 * Test on variety of versions (see ** Heavy Testing)
 
-* Make sure everything is up to date in cvs
+* Make sure everything is up to date in subversion
 
 * Update the versions (see ** Version Numbers) in README, Pg.pm (2 places!), 
Makefile.PL, 
   META.yml, and Changes.
@@ -691,10 +691,10 @@
 are compatible with the foreign key testing. But do try and use them 
 whenever possible.
 
-* "turnstep" in the cvs logs is Greg Sabino Mullane, [EMAIL PROTECTED]
+* "turnstep" in the cvs/svn logs is Greg Sabino Mullane, [EMAIL PROTECTED]
 
 * Use a "tmp" extension for files you keep around in the dbdpg directory, but 
-don't want to show up when you do a "cvs up". They are also ignored by make 
dist.
+don't want to show up when you do a "svn up". They are also ignored by make 
dist.
 
 * Commit each file individually, unless the log message is *really* identical 
 across all committed files (which is rare). Always give a good description 

Reply via email to