Changes between Version 15 and Version 16 of SvnIntro
- Timestamp:
- 01/10/07 16:58:46 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SvnIntro
v15 v16 75 75 76 76 77 == Create an SVN Branch == 77 == SVN Tutorial == 78 79 '''Creating a ROMS_Sed Branch''' 78 80 79 81 Only an administrator can create a branch. Send an email to: etwomey@usgs.gov stating that you would like to be added to the roms_sed trac user group. Please include contact information and perferred username. '''If you are already registered for ROMS, please inlcude your ROMS username.''' Your SVN and ROMS usernames are to be the same to avoid confusion. 80 82 81 == Check to Make Sure You Can See the Repository == 83 '''Check to Make Sure You Can See the Repository''' 82 84 You will need to know your username and password...you should have gotten an e-mail from hosted-projects. 83 85 Right-click and choose {{{Repo-browser}}} from TortoiseSVN.[[BR]] … … 86 88 (You can also navigate the repository with a browser, but cannot do any of the version control stuff that follows). 87 89 88 == Import a Copy of the Trunk == 90 '''Import a Copy of the Trunk''' 89 91 This process brings a copy of main code from the repository to your computer and places it under SVN control.[[BR]] 90 92 Make a directory...name it something meaningful to you, for example {{{bubba_roms_sed}}}[[BR]] … … 113 115 Click OK. 114 116 115 == Create a Branch == 117 '''Create a Branch''' 116 118 In TortoiseSVN, choose {{{Branch/tag}}}. (To see this option in TortoiseSVN, you have to right-click on a directory that is under SVN control...but it does not have to be related to the project at hand).[[BR]] 117 119 From WC at URL:[[BR]] … … 124 126 The branch will exist in the repository...you can repeat the steps above to make a copy of the branch on your computer (but not in the same directory you made in the example above, because that contains a version of the trunk under SVN control).[[BR]] 125 127 126 == Make Changes in Your Branch == 128 '''Make Changes in Your Branch''' 127 129 You can make new files, change existing files, etc. Only existing files will automatically be under SVN control. To add new files, create them in a directory under SVN control (or copy them in from somewhere else).[[BR]] 128 130 Then you can right-click on the filename, and choose {{{Add...}}} under TortoiseSVN, or...[[BR]] … … 130 132 If you compile the code and generate a bunch of .f90 and .o files, or run the model and generate output, they will not be under SVN control unless you add them explicitly. That is usually what you want. (Storing output files here is probably a bad idea, because 1) they tend to be big and take a long time to tranfer to the repository 2) they are binary, so the tools used to compare them will not be useful, and 3) we don't have enough storage space at the repository.) 131 133 132 == Commit Your Changes == 134 '''Commit Your Changes''' 133 135 Navigate to the top directory in your local copy of your branch, e.g., {{{../bubba_roms_sed}}} and right-click. Choose 134 136 {{{SVN Commit...}}}[[BR]] … … 145 147 146 148 147 == Work Cycle == 149 '''Work Cycle''' 148 150 You can Import this branch to another computer...that is the best way to synchronize, say, a desktop at work with a travelling laptop.[[BR]] 149 151 After that, the cycle is:[[BR]]
