From 1638ce7212e350d233337f328a75748f7bacf919 Mon Sep 17 00:00:00 2001 From: Lutz Jaenicke Date: Mon, 11 Feb 2013 11:29:05 +0100 Subject: [PATCH] FAQ/README: we are now using Git instead of CVS (cherry picked from commit f88dbb8385c199a2a28e9525c6bba3a64bda96af) Conflicts: INSTALL.W32 --- FAQ | 2 +- INSTALL.W32 | 4 ++-- README | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/FAQ b/FAQ index fcd6e1a95d..a944640fbf 100644 --- 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 , 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 3dd7832f4e..6c1661f3a9 100644 --- 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 2afe649698..a06265814a 100644 --- 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 -- 2.25.1