Subversion Administration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
You can choose to have one repository per project, or only one single repository containing each project in a separate directory. The single repository setup is easier, but the inconvenient is that the revision number will go up for some projects that did not undergo any changes (if some other projects are updated). | You can choose to have one repository per project, or only one single repository containing each project in a separate directory. The single repository setup is easier, but the inconvenient is that the revision number will go up for some projects that did not undergo any changes (if some other projects are updated). | ||
== Importing projects == | |||
While doing the initial import, remember that if you specify a path, only its contents will be added, thus, if you want to actually add the directory, remember to do a <tt>svn mkdir</tt> first. | |||
== Useful links == | == Useful links == | ||
[http://svnbook.red-bean.com/nightly/en/index.html Subversion book] | [http://svnbook.red-bean.com/nightly/en/index.html Subversion book] | ||
Revision as of 17:26, 16 January 2007
This article is a tutorial to Subversion repository administration.
Design choice: repository setup
You can choose to have one repository per project, or only one single repository containing each project in a separate directory. The single repository setup is easier, but the inconvenient is that the revision number will go up for some projects that did not undergo any changes (if some other projects are updated).
Importing projects
While doing the initial import, remember that if you specify a path, only its contents will be added, thus, if you want to actually add the directory, remember to do a svn mkdir first.