Changes between Version 6 and Version 7 of Documentation/UserGuide/svnBranchePerso

Timestamp:

2019-07-22T16:07:46+02:00 (5 years ago)

Author:

ajornet

Comment:

--

Documentation/UserGuide/svnBranchePerso

@@ -41 +41 @@
 If you have a login to the machine forge where the wiki and svn of ORCHIDEE are stored, you can visualize your account at forge: [https://forge.ipsl.jussieu.fr/orchidee/browser/perso].
 Ask for an account on forge using the email list orchidee-help. This login can be used to modify the wiki, to create and comment tickets and to vizualize your personal folder as well as all branches you have access to. 
+
+== Starting from zero ==
+
+This small guide explains how to properly commit your Orchidee source code into the Subversion for the first time.
+
+If you follow this guide, then the subversion will properly keep track of the modifications done in the code (what you see in svn log).
+
+1. Create a new perso folder in the Subversion to place your files: [wiki:svnBranchePerso#Createyourpersonalfolder Check here]
+
+2. Copy your starting Orchidee version (e.g: orchidee-som revision 5054) to your perso folder (in server). 
+
+{{{
+svn copy -c 5054 svn://forge.ipsl.jussieu.fr/orchidee/branches/ORCHIDEE-SOM/ORCHIDEE svn://forge.ipsl.jussieu.fr/orchidee/perso/haicheng.zhang/ORCHIDEE-MUSLE -m "Branch: some decription here"
+}}}
+
+This step is specially important because it will allow the svn to keep track of any modification done in the code.
+
+3. Download the code from the server to your local machine:
+
+{{{
+svn co svn://forge.ipsl.jussieu.fr/orchidee/perso/haicheng.zhang/ORCHIDEE-MUSLE ORCHSVN-MUSLE
+}}}
+
+4. Bring all the modifications from your code (in local) to the downloaded folder ORCHSVN-MUSLE (in local)
+
+{{{
+cd ORCHSVN-MUSLE
+
+cp /YOUR/ORCH/FOLDER/src_stomate/*90 src_stomate/
+
+cp /YOUR/ORCH/FOLDER/src_sechiba/*90 src_sechiba/
+
+cp /YOUR/ORCH/FOLDER/src_global/*90 src_global/
+
+cp /YOUR/ORCH/FOLDER/src_xml/*xml src_xml/
+
+...
+}}}
+
+For all the src_ folders. Make sure to procede this way to not mess it up with some hidden files.
+
+5. Tell subversion there are new files (if applies)
+
+{{{
+svn add src_somewhere/newfile.f90 -m "New: some explanation here"
+}}}
+
+6. Send the modifications done to the code to the server
+
+{{{
+svn commit -m "New: add some message here"
+}}}
+
+