Changes between Version 3 and Version 4 of gbgp_repository

Timestamp:

2015-10-21T15:05:55Z (9 years ago)

Author:

Dave Offiler

Comment:

--

gbgp_repository

@@ -11 +11 @@
 }}}
 
-For a complete list of Subversion commands see the [http://svnbook.red-bean.com/en/1.0/index.html SVN reference manual]
+For a complete list of Subversion commands see the [http://svnbook.red-bean.com/en/1.7/index.html SVN reference manual (version 1.7)]
 
 '''Checking out trunk'''
 
-To [http://svnbook.red-bean.com/en/1.0/re04.html checkout] the latest development (trunk) versions:
+To [http://svnbook.red-bean.com/en/1.7/svn.tour.initial.html checkout] the latest development (trunk) versions:
 {{{
 svn checkout https://svn.romsaf.org/gbgp/gbgp_src/trunk  ./trunk 
@@ -35 +35 @@
 === Tags ===
 
-A [http://svnbook.red-bean.com/en/1.0/ch04s06.html tag] is just [http://svnbook.red-bean.com/en/1.0/re07.html copy] or snapshot of a a particular revision of the repository. In the case of GBGP, a copy taken from the head of trunk at the time that the distribution files for a release were built. You could just as well checkout the revision number instead, but a tag is easier to remember.
+A [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.tags.html tag] is just a [http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.copy.html copy] or snapshot of a a particular revision of the repository. In the case of GBGP, a copy taken from the head of trunk at the time that the distribution files for a release were built. You could just as well checkout the revision number instead, but a tag is easier to remember.
 
 == Branches ==
 
-Developments to GBGP 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 GBGP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.
+Developments to GBGP should be made from, and committed to, a [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html 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 GBGP. Branches can be temporary and might be for working on resolving a specific Trac Ticket.
 
 Instructions for developers working with branches in GBGP are available [https://trac.romsaf.org/gbgp/wiki/gbgp_branches here].