Fix stray references to cvs.

git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@5188 7894878c-1315-0410-8ee3-d5d059ff63e0

Makefile

@@ -353,7 +353,7 @@ package: version clean
 	find $$lmpackage/ -type f | grep -v ^$$lmpackage/$$lmpackage$$ | \
 	                            grep -v ^$$lmpackage/$$lmpackage.tar$$ | \
 	                            grep -v ^$$lmpackage/$$ | \
-	                            grep -v /CVS | \
+	                            grep -v /\\.svn | \
 	                            grep -v /\\.# | \
 	                            tar rvf $$lmpackage.tar -T -; \
         gzip -9 $$lmpackage.tar ;\
@@ -372,7 +372,7 @@ userpackage: version clean $(KERNELINCLUDEDIR)/sensors.h
 	                            grep -v ^$$lmpackage/kernel/chips | \
 	                            grep -v ^$$lmpackage/kernel/busses | \
 	                            grep -v ^$$lmpackage/$$ | \
-	                            grep -v /CVS | \
+	                            grep -v /\\.svn | \
 	                            grep -v /\\.# | \
 	                            tar rvf $$lmpackage.tar -T -; \
         gzip -9 $$lmpackage.tar ;\

doc/Makefile

@@ -1,11 +1,9 @@
 #
 # quick makefile for the FAQ.
 # So that both the text and html FAQ are accessible on the web
-# (the website points into CVS for the FAQ),
-# they are checked into CVS along with the .texi source.
+# they are checked into SVN along with the .texi source.
 # Don't forget to update version.texi.
 # Run 'make' and then check in all 4 files after editing the .texi source.
-# Or do 'make ci'
 #
 all::  lm_sensors-FAQ.html FAQ
 
@@ -14,6 +12,3 @@ all::  lm_sensors-FAQ.html FAQ
 
 FAQ: lm_sensors-FAQ.texi
 	makeinfo --no-headers --number-sections -o FAQ $<
-
-ci: all
-	cvs ci lm_sensors-FAQ.texi lm_sensors-FAQ.html FAQ version.texi

doc/svn

@@ -18,7 +18,7 @@ To update the code, do a svn update from within the i2c or lm-sensors
 directories. Please read the README and INSTALL files of your working copy
 for how to build the code. Also read the related files in the 'doc' directory
 for info regarding the different bus and chip drivers. Lastly, you can use
-the regular svn commands on the files (like cvs log [filename]) to see the
+the regular svn commands on the files (like svn log [filename]) to see the
 comments made by the developers as changes were made.
 
 If you're not familiar with the use of Subversion we recommend the excellent