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:32:34 +0100
commitda018b129efbfffed766cfdea239c2a6304e9cf9 (patch)
tree1edc1a697f1c9f50752904d102c7c997f794fe97 /README
parente9554f7f9b5bcd03daaa213cb0f6888c7f6e798f (diff)
FAQ/README: we are now using Git instead of CVS
(cherry picked from commit f88dbb8385c199a2a28e9525c6bba3a64bda96af)
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 3c5b7a9a7d..c7a6f845bd 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