[svn:parrot] r36154 - in trunk/docs: . book project

[coke at svn.parrot.org]

Author: coke
Date: Thu Jan 29 20:28:02 2009
New Revision: 36154
URL: https://trac.parrot.org/parrot/log/branches?rev=36154

Log:
Break in the new svn repository by updating some of our docs to point to it.
Robrt++

Modified:
   trunk/docs/book/ch02_getting_started.pod
   trunk/docs/intro.pod
   trunk/docs/parrot.pod
   trunk/docs/project/committer_guide.pod
   trunk/docs/project/release_manager_guide.pod

Modified: trunk/docs/book/ch02_getting_started.pod
==============================================================================
--- trunk/docs/book/ch02_getting_started.pod	Thu Jan 29 18:47:17 2009	(r36153)
+++ trunk/docs/book/ch02_getting_started.pod	Thu Jan 29 20:28:02 2009	(r36154)
@@ -91,10 +91,10 @@
 command into your terminal N<This is for Linux users, on Mac or
 Windows systems, follow the instructions from your SVN client>:
 
-  svn co https://svn.perl.org/parrot/trunk parrot
+  svn co https://svn.parrot.org/parrot/trunk parrot
 
 There's also a web interface for viewing files in the repository at
-U<http://svn.perl.org/parrot/>.
+U<http://svn.parrot.org/parrot/>.
 
 The repository is large and complex, so it's worth taking a little bit
 of time to explore. The code changes constantly, but most files and

Modified: trunk/docs/intro.pod
==============================================================================
--- trunk/docs/intro.pod	Thu Jan 29 18:47:17 2009	(r36153)
+++ trunk/docs/intro.pod	Thu Jan 29 20:28:02 2009	(r36154)
@@ -120,7 +120,7 @@
 project, an awful lot is changing between releases. You can get a copy of the
 latest Parrot from the SVN repository. This is done as follows:
 
-  svn co https://svn.perl.org/parrot/trunk parrot
+  svn co https://svn.parrot.org/parrot/trunk parrot
 
 You can find more instructions at: L<http://www.parrotcode.org/source.html>
 

Modified: trunk/docs/parrot.pod
==============================================================================
--- trunk/docs/parrot.pod	Thu Jan 29 18:47:17 2009	(r36153)
+++ trunk/docs/parrot.pod	Thu Jan 29 20:28:02 2009	(r36154)
@@ -161,7 +161,7 @@
 
 =item * L<http://dev.perl.org/>
 
-=item * L<http://svn.perl.org/>
+=item * L<https://svn.parrot.org/>
 
 =back
 

Modified: trunk/docs/project/committer_guide.pod
==============================================================================
--- trunk/docs/project/committer_guide.pod	Thu Jan 29 18:47:17 2009	(r36153)
+++ trunk/docs/project/committer_guide.pod	Thu Jan 29 20:28:02 2009	(r36154)
@@ -119,8 +119,8 @@
 
 To create a new branch from the parrot trunk you use the command:
 
-  % svn copy https://svn.perl.org/parrot/trunk \
-             https://svn.perl.org/parrot/branches/<branch_name> \
+  % svn copy https://svn.parrot.org/parrot/trunk \
+             https://svn.parrot.org/parrot/branches/<branch_name> \
 	           -m "Creating a private branch of parrot/trunk."
 
 where you might want to be a bit more informative in the commit message than
@@ -133,12 +133,12 @@
 You first need to work out when the branch occurred.  This is done with
 C<svn log>:
 
-  % svn log -v --stop-on-copy https://svn.perl.org/parrot/branches/<branch_name>
+  % svn log -v --stop-on-copy https://svn.parrot.org/parrot/branches/<branch_name>
 
 This will tell you the revision number when the branch happened.  You now
 need a clean working copy of C<trunk>, where you issue the command:
 
-  % svn merge -r<revision_number>:HEAD https://svn.perl.org/parrot/branches/<branch_name>
+  % svn merge -r<revision_number>:HEAD https://svn.parrot.org/parrot/branches/<branch_name>
 
 Run C<svn status>, check the output of C<svn diff> to make sure things look
 sane, build parrot and run the test suite with C<make test> and if
@@ -152,7 +152,7 @@
 C<--stop-on-copy> argument), having a clean working copy of your branch, and
 then running the command:
 
-  % svn merge -r<revision_number>:HEAD https://svn.perl.org/parrot/trunk
+  % svn merge -r<revision_number>:HEAD https://svn.parrot.org/parrot/trunk
 
 Again, build and run the test suite to make sure everything worked (you
 might also have to resolve any conflicts) and then you can check in your
@@ -163,13 +163,13 @@
 It is sometimes necessary to undo a commit.  The best way to do this is with
 a working copy without local modifications, and then issue the command:
 
-  % svn merge -c <revision_number> https://svn.perl.org/parrot/trunk
+  % svn merge -c <revision_number> https://svn.parrot.org/parrot/trunk
 
 This merges I<out> the change which occurred in the C<trunk> branch at the
 revision C<revision_number>.  This command works with Subversion versions
 1.4 and above.  Below this version number, you'll need to use
 
-  % svn merge -r <revision_number>:<revision_number-1> https://svn.perl.org/parrot/trunk
+  % svn merge -r <revision_number>:<revision_number-1> https://svn.parrot.org/parrot/trunk
 
 This merges the change in C<revision_number> I<backwards> so undoes it.
 

Modified: trunk/docs/project/release_manager_guide.pod
==============================================================================
--- trunk/docs/project/release_manager_guide.pod	Thu Jan 29 18:47:17 2009	(r36153)
+++ trunk/docs/project/release_manager_guide.pod	Thu Jan 29 20:28:02 2009	(r36154)
@@ -164,7 +164,7 @@
 you're working in trunk, be sure to specify the revision number generated
 in step 3, above.
 
- $ export SVNPARROT=https://svn.perl.org/parrot
+ $ export SVNPARROT=https://svn.parrot.org/parrot
  $ svn copy -m "tagged release a.b.c" \
    $SVNPARROT/trunk $SVNPARROT/tags/RELEASE_a_b_c
 
@@ -359,7 +359,7 @@
 
 Instead of step 1, create a new branch, and get a working copy of it:
 
-   $ export SVNPARROT=https://svn.perl.org/parrot
+   $ export SVNPARROT=https://svn.parrot.org/parrot
    $ svn copy -m"Starting release a.b.c" \
               $SVNPARROT/trunk $SVNPARROT/branches/RELEASE_a_b_c
    $ svn checkout $SVNPARROT/branches/RELEASE_a_b_c parrot-release