Difference between revisions of "Svn rules - OOP344 20111"
(→checkout) |
|||
| Line 24: | Line 24: | ||
== important commands == | == important commands == | ||
=== checkout === | === checkout === | ||
| − | * is the first thing you do to get a copy of the whole, or part of a repository | + | * is the first thing you do to get a copy of the whole, or part of a repository |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 09:01, 14 January 2011
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
SVN
Standard directories
branches
- in here each team member will create a home direcotry using her/his seneca id
- each of the following home direcotires will contain several direcotories which of them is a work space for different tasks.
email id1
- devbackspace
- leftArrowbug
- workspace 3
- etc....
email id2
email id 3
tags
- holds several direcotries and each of the is a copy of a completed task of trunk
- tags are never to be changed or edited, they are simply copies of success points during the development of the project
trunk
- holds the currect status of the application
- is always in a successful compiled state
How to work with trunk
important commands
checkout
- is the first thing you do to get a copy of the whole, or part of a repository
