[PPL-devel] [GIT] ppl/ppl(master): Updated: we no longer use CVS.

Roberto Bagnara bagnara at cs.unipr.it
Sat Mar 17 15:26:36 CET 2012


Module: ppl/ppl
Branch: master
Commit: 487f91a9655fe5d7fec77b4d24475bd639fa7f75
URL:    http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=487f91a9655fe5d7fec77b4d24475bd639fa7f75

Author: Roberto Bagnara <bagnara at cs.unipr.it>
Date:   Sat Mar 17 15:22:27 2012 +0100

Updated: we no longer use CVS.

---

 README.configure |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.configure b/README.configure
index f4f118e..6987360 100644
--- a/README.configure
+++ b/README.configure
@@ -17,7 +17,7 @@ Contents
 6. Configuring for Optimized Performance
 7. Configuring for Debugging
 8. Programs that Come with the Library
-9. Using the CVS Sources
+9. Using the Git Sources
 
 
 1. The Standard Thing (configure, make, make install)
@@ -437,11 +437,11 @@ In exchange, you will give up an important opportunity to discover
 whether the version of PPL you have built has been miscompiled.
 
 
-9. Using the CVS Sources
+9. Using the Git Sources
 ------------------------
 
-If you use the CVS sources, then you need recent versions of Autoconf
-Automake and Libtool installed.  After a `cvs checkout' or `cvs update'
+If you use the Git sources, then you need recent versions of Autoconf
+Automake and Libtool installed.  After a `git clone' or `git pull'
 you should run the `autoreconf' command.  In case you have fiddled
 around with some of the configuration files, or if you have problems
 you cannot explain otherwise, use `autoreconf -f'.




More information about the PPL-devel mailing list