From ed414d26a0a73c06eec3a2085b1bd34162edaa57 Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Thu, 17 Apr 2008 11:18:18 +0000 Subject: [PATCH] Fix stray references to cvs. git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@5188 7894878c-1315-0410-8ee3-d5d059ff63e0 --- Makefile | 4 ++-- doc/Makefile | 7 +------ doc/svn | 2 +- 3 files changed, 4 insertions(+), 9 deletions(-) diff --git a/Makefile b/Makefile index 2639951f..9fd4534a 100644 --- a/Makefile +++ b/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 ;\ diff --git a/doc/Makefile b/doc/Makefile index 5cf507ed..54aaea58 100644 --- a/doc/Makefile +++ b/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 diff --git a/doc/svn b/doc/svn index 4ce9c984..8e8f94ae 100644 --- a/doc/svn +++ b/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