Cameron Laird's personal index to publicly-accessible CVS repositories
Table of Contents
'Need to see the latest fixes in the source code for a particular
project? I often do. At times like that, I
want the CVSROOT and password for the project. That's the
point of this page. For more detailed information, follow
the links on this page, or
Software Products Using CVS;
the latter complements the data here. Both of these point
to the standard tutorials and introductions to CVS.
Also noteworthy is Philip Greenspun's
Using CVS for
Web development; as with everything Philip writes, I
recommend it, even though I don't agree with it. Note that
the external commenters who appear at the tail of his article
are astute and experienced.
I launched this page a few days before publication of our
introducing CVS to scripting language users.
Stephen Cameron covers much the same territory; he, also, has a page of
CVS Servers he has identified.
If you don't find a particular project or category here, just
ask about it; chances
are I simply haven't unpacked those notes yet.
The Perl core is not publicly accessible through CVS.
- CVSROOT: :pserver:firstname.lastname@example.org:/usr/local/projects/jpl/cvsroot
- password: [blank]
A detailed page on
Access Via CVS" is part of the official
Python language site.
- CVSROOT: :pserver:email@example.com:/projects/cvsroot
- password: snakeoil
for Windows extensions (COM, Win32, Pythonwin, Windows CE)
- CVSROOT: :pserver:firstname.lastname@example.org:/home/cvsroot
- password: anoncvs
of directions on use of its repository. Scriptics
has a nice project-and-branch structure within its
- CVSROOT: :pserver:email@example.com:/cvsroot
- password: cvs
Laird's personal index to publicly-accessible CVS