Updated patch attached. Changes from previous patch:
- do not remove viewcvs from gettingstarted.pod, because it's working again (see #32101)
- do not change viewcvs in glossary.doc to cvsweb, just correct the link
Have a nice day.
Stepan Roh
Index: docs/gettingstarted.pod =================================================================== RCS file: /cvs/public/parrot/docs/gettingstarted.pod,v retrieving revision 1.5 diff -u -r1.5 gettingstarted.pod --- docs/gettingstarted.pod 28 Feb 2004 09:18:02 -0000 1.5 +++ docs/gettingstarted.pod 24 Oct 2004 09:18:23 -0000 @@ -94,7 +94,7 @@ 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>. @@ -293,53 +293,6 @@ 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 Index: docs/glossary.pod =================================================================== RCS file: /cvs/public/parrot/docs/glossary.pod,v retrieving revision 1.12 diff -u -r1.12 glossary.pod --- docs/glossary.pod 28 Feb 2004 00:30:39 -0000 1.12 +++ docs/glossary.pod 24 Oct 2004 09:18:24 -0000 @@ -180,7 +180,7 @@ 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 +http://cvs.perl.org/viewcvs/cvs-public/parrot/lib/Parrot/PackFile.pm?sortby=log =head2 PBC
