commit 09968ee8435bfd18b6b0219b2b5b05a1a9484a5c from: Alexander Barton date: Thu Apr 24 22:13:07 2008 UTC Documentation: get rid of some more references to CVS, switch to GIT. (cherry picked from commit 6e9389b86c906c53a7797b8ced87a19195e16333) commit - 523a6fad097cedd31a6931a29d91bab0d391df63 commit + 09968ee8435bfd18b6b0219b2b5b05a1a9484a5c blob - 8457e8d44aebca2f207aad8dd289d4a434fd048c blob + 33536007c320ce7d29fbf1994f48813e38ff4e4b --- ChangeLog +++ ChangeLog @@ -758,7 +758,3 @@ ngIRCd 0.0.2, 06.01.2002 ngIRCd 0.0.1, 31.12.2001 - erste oeffentliche Version von ngIRCd als "public preview" :-) - - --- -$Id: ChangeLog,v 1.345 2008/03/18 20:12:47 fw Exp $ blob - 227c46264c0a065daba5027186bc67b4d329eee5 blob + 60e7b5ebff45488365786aa582ce93f9215070b3 --- INSTALL +++ INSTALL @@ -51,9 +51,9 @@ on modern UNIX-like systems that are supported by GNU automake ("configure") should be no problem. The normal installation procedure after getting (and expanding) the source -files (using a distribution archive or CVS) is as following: +files (using a distribution archive or GIT) is as following: - 1) ./autogen.sh [only necessary when using CVS] + 1) ./autogen.sh [only necessary when using GIT] 2) ./configure 3) make 4) make install @@ -77,7 +77,7 @@ doc/ directory: sample-ngircd.conf. The first step, autogen.sh, is only necessary if the configure-script isn't already generated. This never happens in official ("stable") releases in -tar.gz-archives, but when using CVS. +tar.gz-archives, but when using GIT. This step is therefore only interesting for developers. @@ -244,7 +244,3 @@ These parameters could be passed to the ngIRCd: Use "--help" to see a short help text describing all available parameters the server understands, with "--version" the ngIRCd shows its version number. In both cases the server exits after the output. - - --- -$Id: INSTALL,v 1.26 2007/04/08 11:39:08 alex Exp $ blob - f01e6d60a04032f397fdec98b998e46544cf4e4f blob + 2eff7bce0c34d5fcd726dfd4a002179f2aeaec2b --- README +++ README @@ -67,9 +67,9 @@ the newest information about the ngIRCd and the most r releases there. If you are interested in the latest development versions (which are not -always stable), then please read the section "CVS" on the homepage and -the file "doc/CVS.txt" which describes the use of CVS, the "Concurrent -Versioning System". +always stable), then please read the section about "GIT" on the homepage and +the file "doc/GIT.txt" which describes the use of GIT, the version control +system used by ngIRCd (homepage: http://git.or.cz/). VI. Bugs @@ -85,7 +85,3 @@ There you can read about known bugs and limitations, t If you have critics, patches or something else, please feel free to post a mail to the ngIRCd mailing list: (please see for details). - - --- -$Id: README,v 1.25 2007/10/04 15:18:48 alex Exp $