Changes between Version 1 and Version 2 of ropp_repository

Timestamp:

2008-03-13T10:07:17Z (16 years ago)

Author:

Huw Lewis

Comment:

Check instructions are ok for creating/checking out branch

ropp_repository

@@ -10 +10 @@
 https://svn.grassaf.org/ropp/
 }}}
-For example, checking out the latest development (trunk) versions:
+
+For a complete list of Subversion commands see the [http://svnbook.red-bean.com/en/1.0/index.html SVN reference manual]
+
+'''Checking out trunk'''
+
+To [http://svnbook.red-bean.com/en/1.0/re04.html checkout] the latest development (trunk) versions:
 {{{
 svn checkout https://svn.grassaf.org/ropp/ropp_src/trunk . 
@@ -16 +21 @@
 svn checkout https://svn.grassaf.org/ropp/ropp_test/trunk .
 }}}
-will check out the source code, documentation, and test folder, respectively to the local working directory.
+This will check out the source code, documentation, and test folder, respectively to the local working directory.
 
-For a complete list of Subversion commands see the [http://svnbook.red-bean.com/en/1.0/index.html SVN reference manual]
 
 == Branches ==
 
-Developments to ROPP should be made from, and committed to, a ''branch'' rather than directly to the latest trunk version. This allows changes to be tested before merging the required changes back into the trunk. The trunk therefore represents a stable 'next potential release' state for ROPP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.
+Developments to ROPP should be made from, and committed to, a [http://svnbook.red-bean.com/en/1.0/ch04.html#svn-ch-4-sect-1 branch] rather than directly to the latest trunk version. This allows changes to be tested before merging the required changes back into the trunk. The trunk therefore represents a stable 'next potential release' state for ROPP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.
 
 '''Creating a branch'''
 
-To create a branch of ropp_src from the trunk use the ''svn copy SRC DST'' command:
+To create a branch of ropp_src from the trunk use the [http://svnbook.red-bean.com/en/1.0/re07.html svn copy ''SRC DST''] command:
 {{{
 svn copy https://svn.grassaf.org/ropp/ropp_src/trunk https://svn.grassaf.org/ropp/ropp_src/branches/dev/Share/<branch_name>
 }}}
-where <branch name> is a name of your choice which should reflect what you are working on. 
+where <branch name> is a name of your choice which should reflect what you are working on. This prompts a text editor where you should describe the purpose of the new branch.
 
-By default it is assumed that you wish to branch from the latest change version of the trunk. The ''-r'' flag can be used to specify the trunk revision from which a branch is required if this is not the latest. The ''-m'' flag should be used when creating a branch to describe the contents of the branch.
+By default it is assumed that you wish to branch from the latest change version of the trunk. The ''-r'' flag can be used to specify the trunk revision from which a branch is required if this is not the latest. The ''-m'' flag could also be used when creating a branch to describe the contents of the branch.
 {{{
 svn copy [-r revision] SRC DST [-m "some text here"]
@@ -49 +53 @@
 
 Code developments are then made and logged within a branch as normal.
-To view the local changes made to a branch, use the ''svn status'' command
+To view the local changes made to a branch, use the [http://svnbook.red-bean.com/en/1.0/re04.html svn status] command.
 
 
 '''Committing changes to a branch''' 
 
-When changes to a branch are ready to be updated in the repository, the code needs to be committed.
+When changes to a branch are ready to be updated in the repository, the code needs to be committed using the [http://svnbook.red-bean.com/en/1.0/re05.html svn commit] command.
 {{{
 svn commit -m "Some text here to describe the changes"