Difference between revisions of "Subversion day to day"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
We can illustrate this using our example project and the command line client. The first step is to checkout a copy of the code: | We can illustrate this using our example project and the command line client. The first step is to checkout a copy of the code: | ||
| + | |||
| + | <pre> | ||
| + | svn checkout http://source.ggy.bris.ac.uk/subversion/myproject/trunk --user-name mylogin workingcopy | ||
| + | </pre> | ||
| + | |||
| + | This creates a new directory, called ''workingcopy'', containing the lastest version of the files on the ''trunk'' of that repository. The ''trunk'' distuinguishes these files from those which may exist on a branch of the repository. Branching is more advanced than we need concern ourselves with at the moment. For now, just note that we will be using the ''trunk'' at all times. | ||
Revision as of 14:13, 7 February 2006
Subversion's Working Cycle
The normal working cycle in terms used by Subversion is:
- checkout/update
- test
- edit
- test
- commit
The Example Project
We can illustrate this using our example project and the command line client. The first step is to checkout a copy of the code:
svn checkout http://source.ggy.bris.ac.uk/subversion/myproject/trunk --user-name mylogin workingcopy
This creates a new directory, called workingcopy, containing the lastest version of the files on the trunk of that repository. The trunk distuinguishes these files from those which may exist on a branch of the repository. Branching is more advanced than we need concern ourselves with at the moment. For now, just note that we will be using the trunk at all times.