summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorLutz Jaenicke <ljaenicke@innominate.com>2013-02-11 11:29:05 +0100
committerLutz Jaenicke <ljaenicke@innominate.com>2013-02-11 11:31:48 +0100
commit1638ce7212e350d233337f328a75748f7bacf919 (patch)
tree0c33a46260ee9b7f2e266efd2cec0fcce7b0db71 /README
parent7ecd974f5f1bb38de6c47c188c8709b86b809245 (diff)
FAQ/README: we are now using Git instead of CVS
(cherry picked from commit f88dbb8385c199a2a28e9525c6bba3a64bda96af) Conflicts: INSTALL.W32
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
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