Changes between Version 1 and Version 2 of SvnTutorial


Ignore:
Timestamp:
02/12/07 03:32:23 (17 years ago)
Author:
arango
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SvnTutorial

    v1 v2  
    11== svn Tutorial ==
    22
    3 In this tutorial, you will learn how to download the ROMS/TOMS source code and create and modify your own branch.
    4 
    5 In the following examples, the username is bubba.
    6 
    7 To proceed, you will need to know your username and password which should have received via e-mail from hosted-projects.
     3In this tutorial, you will learn how to download the ROMS/TOMS source code. To proceed, you will need to know your '''username''' and '''password''' which you selected when filling the ROMS/TOMS registration form.
    84
    95== Check to Make Sure You Can See the Repository ==
     
    5349(See the footnote for correctly installing svn with ssl support on unix style machines below.)
    5450
    55 
    56 == Create a Branch ==
    57 You must use the exact branch name that was created for you by a [wiki:CSTM_Admins CSTM administrator]. If you are unsure of your branch name, check the [https://hosted-projects.com/dav/cmgsoft/nopp/contacts/cmgsoft_acl.txt Access Control List], searching for a line like:
    58 {{{
    59 [roms_sed:/branches/bubba_branch]
    60 }}}
    61 
    62 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]]
    63 From WC at URL:[[BR]]
    64 {{{https://svn1.hosted-projects.com/cmgsoft/roms_sed/trunk}}}[[BR]]
    65 to URL:[[BR]]
    66 {{{https://svn1.hosted-projects.com/cmgsoft/roms_sed/branches/bubba_branch}}}[[BR]]
    67 Click OK.[[BR]]
    68 (stuff streams by...)
    69 
    70 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]]
    71 
    72 == Make Changes in Your Branch ==
    73 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]]
    74 Then you can right-click on the filename, and choose {{{Add...}}} under TortoiseSVN, or...[[BR]]
    75 You will be given an opportunity later (see next step).[[BR]]
    76 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.)
    77 
    78 == Commit Your Changes ==
    79 Navigate to the top directory in your local copy of your branch, e.g., {{{../bubba_roms_sed}}} and right-click. Choose
    80 {{{SVN Commit...}}}[[BR]]
    81 Commit to:  ''{{{https://svn1.hosted-projects.com/cmgsoft/roms_sed/branches/bubba_branch}}}'' [[BR]]
    82 Message:  ''(add a meaningful comment here)'' [[BR]]
    83 Changes made:  ''(Will show files with changes)'' [[BR]]
    84 If the {{{Show unversioned files}}} box is checked, you will see any files you added to the directory. This is your opportunity place them under SVN control. Say you made one named {{{foo}}} that you want to add...check it and[[BR]]
    85 Click OK.
    86 {{{
    87 Adding: bubba_roms_sed\foo 
    88 Sending content: bubba_roms_sed\foo 
    89 Completed: At revision: 244 
    90 }}}
    91 
    92 
    9351== Work Cycle ==
    9452You can Import this branch to another computer...that is the best way to synchronize, say, a desktop at work with a travelling laptop.[[BR]]