[DBD::Pg] Put in some infrastructure for git

Committed by Greg Sabino Mullane <greg-O9fzpki4YnJWk0Htik3J/[email protected]>

Put in some infrastructure for git

---
 .gitignore    |   10 ++++++++++
 Changes       |    3 ++-
 MANIFEST.SKIP |    2 +-
 Makefile.PL   |    2 +-
 README        |    2 --
 README.dev    |   14 +++++++-------
 6 files changed, 21 insertions(+), 12 deletions(-)

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..8c66aa2
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,10 @@
+Makefile
+*.o
+Pg.bs
+Pg.c
+*.xsi
+blib/
+pm_to_blib
+README.testdatabase
+dbdpg_test_database/
+
diff --git a/Changes b/Changes
index b37c1d0..22ba1b2 100644
--- a/Changes
+++ b/Changes
@@ -3,6 +3,8 @@
 
   - Better error message when trying to do things post-disconnect [GSM]
 
+  - Switch from subversion to git. [GSM]
+
 
 Version 2.18.1  Released May 9, 2011
 
@@ -10,7 +12,6 @@ Version 2.18.1  Released May 9, 2011
 
   - Fix bug when async commands issued immediately after a COPY. [GSM] (CPAN bug #68041)
 
-
 Version 2.18.0  Released March 28, 2011 (subversion r14081)
 
   - Thanks to 123people.com for sponsoring work on this release [GSM]
diff --git a/MANIFEST.SKIP b/MANIFEST.SKIP
index 22642e3..bcc0c5b 100644
--- a/MANIFEST.SKIP
+++ b/MANIFEST.SKIP
@@ -22,7 +22,7 @@ testallversions.tmp.pl
 \.log$
 \.blame$
 
-\.svn/*
+\.git/*
 ^tmp/*
 cover_db/
 dbdpg_test_database/*
diff --git a/Makefile.PL b/Makefile.PL
index 31e7e7c..86080b3 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -272,7 +272,7 @@ sub MY::postamble { ## no critic ProhibitQualifiedSubDeclarations
 tags:
 	ctags -f tags --recurse --totals \
 		--exclude=blib \
-		--exclude=.svn \
+		--exclude=.git \
 		--exclude='*~' \
 		--languages=Perl,C --langmap=c:+.h,Perl:+.t \
 
diff --git a/README b/README
index 8ed94e5..a60cbaf 100644
--- a/README
+++ b/README
@@ -17,8 +17,6 @@ The mailing list is at:
 
 The development of DBD::Pg can be tracked at:
 
-    http://svn.perl.org/modules/DBD-Pg/trunk/
-
     git://bucardo.org/dbdpg.git
 
 For information about PostgreSQL, visit:
diff --git a/README.dev b/README.dev
index b6a2ea2..f895146 100644
--- a/README.dev
+++ b/README.dev
@@ -109,7 +109,7 @@ dbdimp.c - The main C file, which does most of the heavy lifting for the DBD::Pg
 dbdimp.h - Header file for dbdimp.c.
 
 dbivport.h - DBI portability macros. This should be the latest version from the 
-  DBI subversion repository.
+  DBI git repository.
 
 Pg.pm - The main Perl file, which contains DBD::Pg packages and code for the 
   methods. Often times code here calls code from Pg.xs and dbdimp.c.
@@ -540,7 +540,7 @@ please check that you have done the following items:
 
 * Created a standard header for the file, with a (dollar sign)Id(dollar sign)
 
-* Added it to subversion via 'svn add filename' and 'svn commit filename'
+* Added it to git via 'git add filename' and git commit filename'
 
 * Added it to the MANIFEST file
 
@@ -571,7 +571,7 @@ other sections referenced herein (indicated with **)
 
 * Test on variety of versions (see ** Heavy Testing), including the optional tests.
 
-* Make sure everything is up to date in subversion
+* Make sure everything is up to date in git (git status)
 
 * Update the versions (see ** Version Numbers) in README, Pg.pm (2 places!), Makefile.PL, 
   lib/Bundle/DBD/Pg.pm, META.yml (3 places!), and Changes. Run the t/00_release.t file 
@@ -595,7 +595,7 @@ http://search.cpan.org/dist/DBD-Pg/
 
 * Completely update the Changes file
 
-The best way to do this (other than doing it as you go along) is to check the subversion logs, 
+The best way to do this (other than doing it as you go along) is to check the git logs, 
 by running a diff against the last-released version.
 
 * Update the documentation
@@ -642,7 +642,7 @@ You'll need the pause account password. The interface is fairly straightforward.
 is loaded, wait for it to appear on the main DBD::Pg page and then test that the file 
 has the same checksums.
 
-* Commit the SIGNATURE file. Remember the subversion revision number given, and add that 
+* Commit the SIGNATURE file. Remember the git commit hash given, and add that 
 to the Changes files. Then commit the Changes file.
 
 * Announce to the "public" lists
@@ -705,10 +705,10 @@ not persistent across tests, they mess up the schema testing, and they
 are not compatible with the foreign key testing. But do try and use them 
 whenever possible.
 
-* "turnstep" in the cvs/svn logs is Greg Sabino Mullane, [email protected]
+* "turnstep" in the cvs/svn/git 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 "svn up". They are also ignored by make dist.
+don't want to show up when you do a "git status". 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 
-- 
1.7.0.5