FAQ/README: we are now using Git instead of CVS

(cherry picked from commit f88dbb8385c199a2a28e9525c6bba3a64bda96af)

diff --git a/FAQ b/FAQ
index 0b9d60c32abd37be6117650a0ec08940303adda5..c01365d7da3f90debbf1936ecf2eae478535cdcf 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -87,7 +87,7 @@ OpenSSL 1.0.1c was released on May 10, 2012.
 
 In addition to the current stable release, you can also access daily
 snapshots of the OpenSSL development version at <URL:
-ftp://ftp.openssl.org/snapshot/>, or get it by anonymous CVS access.
+ftp://ftp.openssl.org/snapshot/>, or get it by anonymous Git access.
 
 
 * Where is the documentation?

diff --git a/INSTALL.W32 b/INSTALL.W32
index d23c4baf625e783bda70830629d019cb835b66a9..80e538273e996b61ae79662719bb4972f232df42 100644 (file)
--- a/INSTALL.W32
+++ b/INSTALL.W32
@@ -29,7 +29,7 @@
   is required if you intend to utilize assembler modules. Note that NASM
   is now the only supported assembler.
 
- If you are compiling from a tarball or a CVS snapshot then the Win32 files
+ If you are compiling from a tarball or a Git snapshot then the Win32 files
  may well be not up to date. This may mean that some "tweaking" is required to
  get it all to work. See the trouble shooting section later on for if (when?)
  it goes wrong.
@@ -257,7 +257,7 @@
 
  then ms\do_XXX should not give a warning any more. However the numbers that
  get assigned by this technique may not match those that eventually get
- assigned in the CVS tree: so anything linked against this version of the
+ assigned in the Git tree: so anything linked against this version of the
  library may need to be recompiled.
 
  If you get errors about unresolved symbols there are several possible

diff --git a/README b/README
index 05198344260fe56e4c834d672d9bcb3fcc95b93e..b42dd1c8c7ba36b7a31defc209983130911bbf3f 100644 (file)
--- a/README
+++ b/README
@@ -190,7 +190,7 @@
  reason as to why that feature isn't implemented.
 
  Patches should be as up to date as possible, preferably relative to the
- current CVS or the last snapshot. They should follow the coding style of
+ current Git or the last snapshot. They should follow the coding style of
  OpenSSL and compile without warnings. Some of the core team developer targets
  can be used for testing purposes, (debug-steve64, debug-geoff etc). OpenSSL
  compiles on many varied platforms: try to ensure you only use portable