Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Update 'docs' WRT to the switch to subversion.

Based on the patches from stepan@srnet.cz,
[perl #32118], http://rt.perl.org/rt3/Ticket/Display.html?id=32118


git-svn-id: https://svn.parrot.org/parrot/trunk@8118 d31e2699-5ff4-0310-a27c-f18f2fbe73fe
  • Loading branch information...
commit b103d209abccc04b375ad703a7e9dd10b34c6308 1 parent 46b993d
@bschmalhofer bschmalhofer authored
View
2  docs/ROADMAP
@@ -76,7 +76,7 @@ compatibility will be listed here.
=item *
-To be included: docs/pmc, docs/resources, docs/*.pod, anything in CVS not
+To be included: docs/pmc, docs/resources, docs/*.pod, anything in SVN not
in docs, RT. (That is, quite a bit.)
=back
View
4 docs/debugger.pod
@@ -1,4 +1,4 @@
-# Copyright: 2001-2004 The Perl Foundation. All Rights Reserved.
+# Copyright: 2001-2005 The Perl Foundation. All Rights Reserved.
# $Id$
=head1 NAME
@@ -458,7 +458,7 @@ data used by the debugger.
=item Version 1.0
-First version (CVS debug.c revision 1.24), authored by Aldo Calpini
+First version (SVN debug.c revision 1.24), authored by Aldo Calpini
=back
View
2  docs/faq.pod
@@ -546,7 +546,7 @@ Really.: http://developer.apple.com/techpubs/mac/PPCSoftware/PPCSoftware-13.html
=head1 VERSION
The FAQ is now in version control and "Revision" isn't really being tracked.
-The most recent CVS ID is C<$Id$>
+The most recent SVN ID is C<$Id$>
=over 4
View
81 docs/gettingstarted.pod
@@ -1,4 +1,4 @@
-# Copyright: 2001-2004 The Perl Foundation. All Rights Reserved.
+# Copyright: 2001-2005 The Perl Foundation. All Rights Reserved.
# $Id$
=head1 NAME
@@ -19,43 +19,37 @@ through the questions below and read the ones that apply to you.
=item *
-If you're just interested in browsing the CVS repository without downloading
-anything, a few interfaces exist.
+There is a webinterface to the subversion repository, in case you just want to browse
+the source.
-http://cvs.perl.org/cvsweb/parrot/
-
-http://cvs.perl.org/viewcvs/parrot/
+http://svn.perl.org/viewcvs/parrot/
=item *
-The easiest solution is to grab the most recent snapshot of the Parrot CVS
+The easiest solution is to grab the most recent snapshot of the Parrot SVN
repository. It's a tar-gzipped download of a recent checkout of Parrot,
updated every six hours. You can find it here:
-http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz
+http://svn.perl.org/snapshots/parrot/parrot-latest.tar.gz
=item *
-Even better is the option to use CVS, which gets you the very latest copy of
+Even better is the option to use SVN, which gets you the very latest copy of
the Parrot distribution. The procedure for this is:
-C<cvs -d :pserver:anonymous@cvs.perl.org:/cvs/public login>
-
-C<[press enter at the password prompt]>
-
-C<cvs -d :pserver:anonymous@cvs.perl.org:/cvs/public co parrot>
+C<svn checkout https://svn.perl.org/parrot/trunk parrot>
=item *
Or, if you're one of those rsync folks, you can access the repository with:
-C<rsync -av --delete cvs.perl.org::parrot-HEAD parrot>
+C<rsync -av --delete svn.perl.org::parrot-HEAD parrot>
=back
-For the Parrot CVS website with the above instructions, check out:
+The abobe instructions are also on the Parrot website:
-http://cvs.perl.org/
+http://www.parrotcode.org/source.html
=head2 Now that I've got Parrot, what do I do?
@@ -94,7 +88,7 @@ There is also some experimental auto-generated HTML documentation
available by running the following command in the Parrot distribution's
root directory:
- % perl tools/docs/write_docs.pl -s
+ % make html
To view the HTML documentation start with the page F<docs/html/index.html>.
@@ -193,7 +187,7 @@ http://lists.perl.org/showlist.cgi?name=perl6-announce
=back
-In addition, there is a mailing list which logs all commits to the Parrot CVS
+In addition, there is a mailing list which logs all commits to the Parrot SVN
repository. If you're interested in Parrot development, you might find it
very helpful to subscribe and keep up on changes that people are making.
@@ -289,57 +283,10 @@ Located at:
http://www.vendian.org/parrot/wiki/
A collection of various other pieces of useful Parrot information and
-documentation that have yet to make it into the CVS repository. Includes
+documentation that have yet to make it into the SVN repository. Includes
a comprehensive guide to getting started with Parrot development (called,
unsurprisingly, 'Getting Started with Parrot Development').
-=item * Tinderbox
-
-The tinderbox consists of a number of different computers running various OS
-and platform configurations, downloading the latest Parrot distribution every
-few hours and running the test suite to verify that it works on that given
-combination of software and hardware.
-
-To view the results of the tinderbox system, check out:
-
-http://tinderbox.perl.org/tinderbox/bdshowbuild.cgi?tree=parrot
-
-=item * Tinderbox Failure Summary
-
-A brief summary of the current status of the various tinderbox machines.
-Useful for finding out which tests are failing (if any).
-
-=item * Test Coverage Results
-
-The Parrot test suite is intended to test all aspects of Parrot's code. You
-can see how successful we are at this goal by checkout the test coverage. It
-gives line, branch, and call coverage percentages on a per-file or
-per-function breakdown. Find it here:
-
-http://www.hitchhiker.org/parrot_coverage/
-
-=item * Bonsai
-
-Bonsai is a cvs tree control tool to monitor the status of cvs trees.
-Whenever a checkin occurs, bonsai adds that person to the "hook," a list of
-those responsible for the current state of the tree (this should be cleared
-whenever we know that things are working for sure). Users can then run
-queries to find out who has changed what files and access their checkin
-comments in addition to generating diffs.
-
-=over 4
-
-=item * Query
-
-http://tinderbox.perl.org/bonsai/cvsqueryform.cgi?cvsroot=/home/tinder/perlcvs&module=parrot
-
-=item * Browse
-
-http://tinderbox.perl.org/bonsai/rview.cgi?cvsroot=/home/tinder/perlcvs&dir=parrot&module=parrot
-
-
-=back
-
=back
=head1 VERSION
View
7 docs/glossary.pod
@@ -1,4 +1,4 @@
-# Copyright: 2001-2004 The Perl Foundation. All Rights Reserved.
+# Copyright: 2001-2005 The Perl Foundation. All Rights Reserved.
# $Id$
=head1 NAME
@@ -177,10 +177,7 @@ run PBC files, PASM files or IMC files).
=head2 Packfile
Another name for a PBC file, due to the names used for data structures
-in one of the early implementations. You can see the initial commit of
-the PackFile.pm implementation, with the rationale for the name here:
-
-http://cvs.perl.org/cgi/viewcvs.cgi/parrot/lib/Parrot/PackFile.pm?sortby=log
+in one of the early implementations in Perl5.
=head2 PBC
View
4 docs/parrot.pod
@@ -1,4 +1,4 @@
-# Copyright: 2001-2004 The Perl Foundation. All Rights Reserved.
+# Copyright: 2001-2005 The Perl Foundation. All Rights Reserved.
# $Id$
=head1 NAME
@@ -157,7 +157,7 @@ See:
=item * http://dev.perl.org/
-=item * http://cvs.perl.org/
+=item * http://svn.perl.org/
=item * http://www.parrotcode.org/
View
6 docs/pdds/pdd07_codingstd.pod
@@ -1,4 +1,4 @@
-# Copyright: 2001-2004 The Perl Foundation. All Rights Reserved.
+# Copyright: 2001-2005 The Perl Foundation. All Rights Reserved.
# $Id$
=head1 NAME
@@ -630,9 +630,9 @@ The POD documentation should follow the standard POD layout:
The Parrot copyright statement.
-=item CVS
+=item SVN
-A CVS id string.
+A SVN id string.
=item NAME
View
20 docs/submissions.pod
@@ -1,3 +1,6 @@
+# Copyright: 2004-2005 The Perl Foundation. All Rights Reserved.
+# $Id$
+
=head1 NAME
docs/submissions.pod - Parrot Submission Instructions
@@ -56,10 +59,17 @@ F<parrot.new> and run a recursive C<diff> on the two directories to
create your patch. The C<diff> should be created in F<parrotdev>.
cd parrotdev
- diff -ur --exclude=CVS parrot parrot.new > docs.patch
+ diff -ur --exclude='.svn' parrot parrot.new > docs.patch
OS X users should also include C<--exclude=.DS_Store>.
+=item C<svn>
+
+Patches can also be generated by svn.
+
+ cd parrotdev
+ svn diff > docs.patch
+
=back
=item 2
@@ -100,7 +110,7 @@ Send the mail.
=head2 Applying Patches
You may wish to apply a patch submitted by someone else before the patch
-is incorporated into CVS.
+is incorporated into SVN.
For single C<diff> patches, copy the patch file to F<parrot>, and run:
@@ -161,10 +171,10 @@ reply with details of the ticket identifier. This identifier should be
used in all further correspondence concerning the submission.
Everyone on the list sees the submission, and can comment on it. A
-developer with CVS commit authority will commit it to CVS once it is
+developer with SVN commit authority will commit it to SVN once it is
clear that it is the right thing to do.
-Even those developers with CVS commit authority stick to this scheme for
+Even those developers with SVN commit authority stick to this scheme for
all but the most trivial of their own patches, to allow time for peer
review of their changes.
@@ -179,3 +189,5 @@ L<http://www.parrotcode.org/openpatches.html>
Adapted by Michael Scott from a tutorial submitted by Aldo Calpini, with
some additional remarks from Bruce Gray.
+
+=cut
Please sign in to comment.
Something went wrong with that request. Please try again.