http://cvshome.org no longer related to CVS version control.

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

http://cvshome.org no longer related to CVS version control.

Matteo Niccoli-2
Hello,

reading the cvs man page I realized that there are a lot of references to
the cvshome.org site , but it is not the cvs home page anymore. Maybe it
should be changed to https://www.nongnu.org/cvs/?
Reply | Threaded
Open this post in threaded view
|

Re: http://cvshome.org no longer related to CVS version control.

Matteo Niccoli-2
Sorry, not man page. I mean running just cvs command:

The Concurrent Versions System (CVS) is a tool for version control.
For CVS updates and additional information, see
    the CVS home page at http://www.cvshome.org/ or
    Pascal Molli's CVS site at http://www.loria.fr/~molli/cvs-index.html


On Mon, 7 Jan 2019 at 11:01, Matteo Niccoli <[hidden email]> wrote:

> Hello,
>
> reading the cvs man page I realized that there are a lot of references to
> the cvshome.org site , but it is not the cvs home page anymore. Maybe it
> should be changed to https://www.nongnu.org/cvs/?
>
Reply | Threaded
Open this post in threaded view
|

Re: http://cvshome.org no longer related to CVS version control.

Jeremie Courreges-Anglas-2

(top-posting edited)

> On Mon, 7 Jan 2019 at 11:01, Matteo Niccoli <[hidden email]> wrote:
>
>> Hello,
>>
>> reading the cvs man page I realized that there are a lot of references to
>> the cvshome.org site , but it is not the cvs home page anymore.

I remember some people being confused in the past, maybe this could be
improved.  And the easiest way to do that would be to just delete those
links.

>> Maybe it
>> should be changed to https://www.nongnu.org/cvs/?

I'm not sure we should point people at upstream cvs.  We're not shipping
the latest version, but an old release before the licensing change.
We should not mislead people into thinking that:
- they should report bugs upstream
- they can expect cvs on OpenBSD to act like newer cvs on other systems

If we want to point people at documentation, the Cederqvist[1] is nice
and could be an addition to the books category in ports.

There's also the CVS book[2] but I've never read it.

What do others think?

On Mon, Jan 07 2019, Matteo Niccoli <[hidden email]> wrote:
> Sorry, not man page. I mean running just cvs command:
>
> The Concurrent Versions System (CVS) is a tool for version control.
> For CVS updates and additional information, see
>     the CVS home page at http://www.cvshome.org/ or
>     Pascal Molli's CVS site at http://www.loria.fr/~molli/cvs-index.html

The manpage and info page also list cvshome.org and loria.fr.

[1] https://ftp.gnu.org/non-gnu/cvs/source/stable/1.11.23/cederqvist-1.11.23.pdf
[2] http://cvsbook.red-bean.com/
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply | Threaded
Open this post in threaded view
|

Re: http://cvshome.org no longer related to CVS version control.

Alexander Bluhm
On Tue, Jan 08, 2019 at 05:13:11PM +0100, Jeremie Courreges-Anglas wrote:
> >> reading the cvs man page I realized that there are a lot of references to
> >> the cvshome.org site , but it is not the cvs home page anymore.
>
> I remember some people being confused in the past, maybe this could be
> improved.  And the easiest way to do that would be to just delete those
> links.

Just remove the link from the usage.  If people want to find
docmumentation, they should look into the man page or use a web
search engine.

bluhm

Reply | Threaded
Open this post in threaded view
|

Re: http://cvshome.org no longer related to CVS version control.

Jeremie Courreges-Anglas-2
On Tue, Jan 08 2019, Alexander Bluhm <[hidden email]> wrote:

> On Tue, Jan 08, 2019 at 05:13:11PM +0100, Jeremie Courreges-Anglas wrote:
>> >> reading the cvs man page I realized that there are a lot of references to
>> >> the cvshome.org site , but it is not the cvs home page anymore.
>>
>> I remember some people being confused in the past, maybe this could be
>> improved.  And the easiest way to do that would be to just delete those
>> links.
>
> Just remove the link from the usage.  If people want to find
> docmumentation, they should look into the man page or use a web
> search engine.

Here's a diff that kills all occurrences of loria.fr and cvshome.org
(plus sourrounding fluff) in the *installed* files.

Objections/oks?


Index: contrib/README
===================================================================
RCS file: /cvs/src/gnu/usr.bin/cvs/contrib/README,v
retrieving revision 1.1.1.9
diff -u -p -r1.1.1.9 README
--- contrib/README 28 Feb 1999 21:34:13 -0000 1.1.1.9
+++ contrib/README 9 Jan 2019 20:04:33 -0000
@@ -20,11 +20,6 @@ If you have some software that works wit
 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.
Index: doc/cvs.texinfo
===================================================================
RCS file: /cvs/src/gnu/usr.bin/cvs/doc/cvs.texinfo,v
retrieving revision 1.3
diff -u -p -r1.3 cvs.texinfo
--- doc/cvs.texinfo 4 Sep 2016 06:07:47 -0000 1.3
+++ doc/cvs.texinfo 9 Jan 2019 20:04:34 -0000
@@ -246,16 +246,6 @@ In April, 1989, Brian Berliner designed
 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
@@ -13622,24 +13612,6 @@ fix for inclusion in future releases of
 the file @sc{hacking} in the @sc{cvs} source
 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}.
Index: doc/cvsclient.texi
===================================================================
RCS file: /cvs/src/gnu/usr.bin/cvs/doc/cvsclient.texi,v
retrieving revision 1.1.1.18
diff -u -p -r1.1.1.18 cvsclient.texi
--- doc/cvsclient.texi 28 Sep 2001 22:45:42 -0000 1.1.1.18
+++ doc/cvsclient.texi 9 Jan 2019 20:04:34 -0000
@@ -2004,8 +2004,6 @@ working directory, and the meaning of se
 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
Index: man/cvs.1
===================================================================
RCS file: /cvs/src/gnu/usr.bin/cvs/man/cvs.1,v
retrieving revision 1.12
diff -u -p -r1.12 cvs.1
--- man/cvs.1 3 Jun 2013 17:02:36 -0000 1.12
+++ man/cvs.1 9 Jan 2019 20:04:34 -0000
@@ -2140,7 +2140,6 @@ For CVS updates, more information on doc
 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 ),
Index: src/main.c
===================================================================
RCS file: /cvs/src/gnu/usr.bin/cvs/src/main.c,v
retrieving revision 1.42
diff -u -p -r1.42 main.c
--- src/main.c 17 Nov 2015 12:26:47 -0000 1.42
+++ src/main.c 9 Jan 2019 20:04:35 -0000
@@ -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,
 };
 


--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply | Threaded
Open this post in threaded view
|

Re: http://cvshome.org no longer related to CVS version control.

Alexander Bluhm
On Wed, Jan 09, 2019 at 09:07:40PM +0100, Jeremie Courreges-Anglas wrote:

> On Tue, Jan 08 2019, Alexander Bluhm <[hidden email]> wrote:
> > On Tue, Jan 08, 2019 at 05:13:11PM +0100, Jeremie Courreges-Anglas wrote:
> >> >> reading the cvs man page I realized that there are a lot of references to
> >> >> the cvshome.org site , but it is not the cvs home page anymore.
> >>
> >> I remember some people being confused in the past, maybe this could be
> >> improved.  And the easiest way to do that would be to just delete those
> >> links.
> >
> > Just remove the link from the usage.  If people want to find
> > docmumentation, they should look into the man page or use a web
> > search engine.
>
> Here's a diff that kills all occurrences of loria.fr and cvshome.org
> (plus sourrounding fluff) in the *installed* files.
>
> Objections/oks?

OK bluhm@

> Index: contrib/README
> ===================================================================
> RCS file: /cvs/src/gnu/usr.bin/cvs/contrib/README,v
> retrieving revision 1.1.1.9
> diff -u -p -r1.1.1.9 README
> --- contrib/README 28 Feb 1999 21:34:13 -0000 1.1.1.9
> +++ contrib/README 9 Jan 2019 20:04:33 -0000
> @@ -20,11 +20,6 @@ If you have some software that works wit
>  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.
> Index: doc/cvs.texinfo
> ===================================================================
> RCS file: /cvs/src/gnu/usr.bin/cvs/doc/cvs.texinfo,v
> retrieving revision 1.3
> diff -u -p -r1.3 cvs.texinfo
> --- doc/cvs.texinfo 4 Sep 2016 06:07:47 -0000 1.3
> +++ doc/cvs.texinfo 9 Jan 2019 20:04:34 -0000
> @@ -246,16 +246,6 @@ In April, 1989, Brian Berliner designed
>  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
> @@ -13622,24 +13612,6 @@ fix for inclusion in future releases of
>  the file @sc{hacking} in the @sc{cvs} source
>  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}.
> Index: doc/cvsclient.texi
> ===================================================================
> RCS file: /cvs/src/gnu/usr.bin/cvs/doc/cvsclient.texi,v
> retrieving revision 1.1.1.18
> diff -u -p -r1.1.1.18 cvsclient.texi
> --- doc/cvsclient.texi 28 Sep 2001 22:45:42 -0000 1.1.1.18
> +++ doc/cvsclient.texi 9 Jan 2019 20:04:34 -0000
> @@ -2004,8 +2004,6 @@ working directory, and the meaning of se
>  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
> Index: man/cvs.1
> ===================================================================
> RCS file: /cvs/src/gnu/usr.bin/cvs/man/cvs.1,v
> retrieving revision 1.12
> diff -u -p -r1.12 cvs.1
> --- man/cvs.1 3 Jun 2013 17:02:36 -0000 1.12
> +++ man/cvs.1 9 Jan 2019 20:04:34 -0000
> @@ -2140,7 +2140,6 @@ For CVS updates, more information on doc
>  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 ),
> Index: src/main.c
> ===================================================================
> RCS file: /cvs/src/gnu/usr.bin/cvs/src/main.c,v
> retrieving revision 1.42
> diff -u -p -r1.42 main.c
> --- src/main.c 17 Nov 2015 12:26:47 -0000 1.42
> +++ src/main.c 9 Jan 2019 20:04:35 -0000
> @@ -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,
>  };
>  
>
>
> --
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE