| 33 | | To check out a copy of '''trunk''', a branch, a tagged version, or a sandbox, you need to know the ''URL'' and use {{{svn checkout <url>}}}. For instance: |
| 34 | | |
| 35 | | * {{{svn co http://svn.osgeo.org/fusion/trunk}}} - check out trunk |
| 36 | | * {{{svn co http://svn.osgeo.org/fusion/branches/fusion-1.0}}} - check out the branch for version 1.0 |
| 37 | | * {{{svn co http://svn.osgeo.org/fusion/tags/fusion-1.0.0}}} - check out the 1.0.0 released version |
| 38 | | * {{{svn co http://svn.osgeo.org/fusion/sandbox/pagameba}}} - check out pagameba's sandbox |
| 39 | | |
| 40 | | Once you have a checked out copy, this is called a working copy. To update a working copy to the latest version, you use the ''update'' command with no arguments: |
| 41 | | |
| 42 | | * {{{svn update}}} |
| 43 | | |
| 44 | | To move the working copy to a specific revision number, you can add the ''revision'' parameter: |
| 45 | | |
| 46 | | * {{{svn update -r <revision>}}} |
| 47 | | |
| 48 | | To see if you have changes in your working copy against the current revision: |
| 49 | | |
| 50 | | * {{{svn status}}} |
| 51 | | |
| 52 | | To see the differences between your working copy and the current revision: |
| 53 | | |
| 54 | | * {{{svn diff}}} |
| 55 | | * {{{svn diff > diff.patch}}} redirects the output to a file that is suitable for using with the {{{patch}}} command |
| | 35 | Fusion user documentation is maintained primarily in in the [wiki:Documentation] section of this wiki. The API documentation is maintained in the Fusion code using [http://www.naturaldocs.org/ NaturalDocs]. See the [wiki:DocumentationStandards documentation standards page] for details on documenting your code. |
