Drop dead links to loria.fr and cvshome.org

Pointed out by Matteo Niccoli, ok bluhm@ sthen@

5 files changed, 0 insertions, 54 deletions

diff --git a/gnu/usr.bin/cvs/contrib/README b/gnu/usr.bin/cvs/contrib/README
index 8a93f8f689b..613527ba64d 100644
--- a/gnu/usr.bin/cvs/contrib/README
+++ b/gnu/usr.bin/cvs/contrib/README
@@ -20,11 +20,6 @@ If you have some software that works with CVS that you wish to offer it
 is suggested that you make it available by FTP or HTTP and then announce
 it on the info-cvs mailing list.
 
-There is a web page of software related to CVS at the following URL which
-would presumably be willing to list your software.
-
-	http://www.loria.fr/~molli/cvs-index.html
-
 An attempt at a table of Contents for this directory:
 
 	README		This file.
diff --git a/gnu/usr.bin/cvs/doc/cvs.texinfo b/gnu/usr.bin/cvs/doc/cvs.texinfo
index 0dcdcf40f43..9c75e882e74 100644
--- a/gnu/usr.bin/cvs/doc/cvs.texinfo
+++ b/gnu/usr.bin/cvs/doc/cvs.texinfo
@@ -246,16 +246,6 @@ In April, 1989, Brian Berliner designed and coded @sc{cvs}.
 Jeff Polk later helped Brian with the design of the @sc{cvs}
 module and vendor branch support.
 
-@cindex Source, getting CVS source
-You can get @sc{cvs} in a variety of ways, including
-free download from the internet.  For more information
-on downloading @sc{cvs} and other @sc{cvs} topics, see:
-
-@example
-http://www.cvshome.org/
-http://www.loria.fr/~molli/cvs-index.html
-@end example
-
 @cindex Mailing list
 @cindex List, mailing list
 @cindex Newsgroups
@@ -13624,24 +13614,6 @@ distribution.  It contains much more information on the
 process of submitting fixes.
 
 @item
-There may be resources on the net which can help.  Two
-good places to start are:
-
-@example
-http://www.cvshome.org
-http://www.loria.fr/~molli/cvs-index.html
-@end example
-
-If you are so inspired, increasing the information
-available on the net is likely to be appreciated.  For
-example, before the standard @sc{cvs} distribution
-worked on Windows 95, there was a web page with some
-explanation and patches for running @sc{cvs} on Windows
-95, and various people helped out by mentioning this
-page on mailing lists or newsgroups when the subject
-came up.
-
-@item
 It is also possible to report bugs to @code{bug-cvs}.
 Note that someone may or may not want to do anything
 with your bug report---if you need a solution consider
diff --git a/gnu/usr.bin/cvs/doc/cvsclient.texi b/gnu/usr.bin/cvs/doc/cvsclient.texi
index b81a7736c56..8996ee4fade 100644
--- a/gnu/usr.bin/cvs/doc/cvsclient.texi
+++ b/gnu/usr.bin/cvs/doc/cvsclient.texi
@@ -2004,8 +2004,6 @@ working directory, and the meaning of sending @code{Entries} without
 A number of enhancements are possible.  Also see the file @sc{todo} in
 the @sc{cvs} source distribution, which has further ideas concerning
 various aspects of @sc{cvs}, some of which impact the protocol.
-Similarly, the @code{http://www.cvshome.org} site, in particular the
-@cite{Development} pages.
 
 @itemize @bullet
 @item
diff --git a/gnu/usr.bin/cvs/man/cvs.1 b/gnu/usr.bin/cvs/man/cvs.1
index 58fb3ee566a..511b028217b 100644
--- a/gnu/usr.bin/cvs/man/cvs.1
+++ b/gnu/usr.bin/cvs/man/cvs.1
@@ -2140,7 +2140,6 @@ For CVS updates, more information on documentation, software related
 to CVS, development of CVS, and more, see:
 .in +1i
 .B http://www.cyclic.com
-.B http://www.loria.fr/~molli/cvs-index.html
 .in -1i
 .sp
 .BR ci ( 1 ),
diff --git a/gnu/usr.bin/cvs/src/main.c b/gnu/usr.bin/cvs/src/main.c
index ea120fae8ce..438ca67c783 100644
--- a/gnu/usr.bin/cvs/src/main.c
+++ b/gnu/usr.bin/cvs/src/main.c
@@ -176,24 +176,6 @@ static const char *const usg[] =
     "    (specify -H followed by a command name for command-specific help)\n",
     "  Specify --help to receive this message\n",
     "\n",
-
-    /* Some people think that a bug-reporting address should go here.  IMHO,
-       the web sites are better because anything else is very likely to go
-       obsolete in the years between a release and when someone might be
-       reading this help.  Besides, we could never adequately discuss
-       bug reporting in a concise enough way to put in a help message.  */
-
-    /* I was going to put this at the top, but usage() wants the %s to
-       be in the first line.  */
-    "The Concurrent Versions System (CVS) is a tool for version control.\n",
-    /* I really don't think I want to try to define "version control"
-       in one line.  I'm not sure one can get more concise than the
-       paragraph in ../cvs.spec without assuming the reader knows what
-       version control means.  */
-
-    "For CVS updates and additional information, see\n",
-    "    the CVS home page at http://www.cvshome.org/ or\n",
-    "    Pascal Molli's CVS site at http://www.loria.fr/~molli/cvs-index.html\n",
     NULL,
 };