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

(cherry picked from commit f88dbb8385c199a2a28e9525c6bba3a64bda96af)

Conflicts:

	INSTALL.W32

diff --git a/FAQ b/FAQ
index fcd6e1a95dd513a760f08c05a4fbb67afaaeef79..a944640fbfe04618e56d3bd61efafcc28e8d2254 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -87,7 +87,7 @@ OpenSSL 1.0.1d was released on Feb 5th, 2013.
 
 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 3dd7832f4eae0f498352966073e44ff4a13f729a..6c1661f3a9e3e18696bdba4bf1a221be8f87363a 100644 (file)
--- a/INSTALL.W32
+++ b/INSTALL.W32
@@ -18,7 +18,7 @@
   * Borland C
   * GNU C (Cygwin or MinGW)
 
- 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.
@@ -264,7 +264,7 @@ To install OpenSSL to the specified location do:
 
  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 2afe64969856202c99ff6cc728f8ca96dd7fad58..a06265814ade2461846e2f9c7f74124e70226e8a 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