Difference between revisions of "Slicer3:Contributing codes to Slicer3"
Line 11: | Line 11: | ||
'''You don't need to obtain an account''' if you don't commit codes back to the sever, but we enthusiastically invite you to do so. | '''You don't need to obtain an account''' if you don't commit codes back to the sever, but we enthusiastically invite you to do so. | ||
− | == How | + | == How to commit codes == |
− | First, fill the form at https://www.kitware.com/Admin/SendPassword.cgi and under Comment type "Request password for NA-MIC Sandbox". Once you have access to write to SVN, you can work with repository using the following commands: | + | First, fill the form at https://www.kitware.com/Admin/SendPassword.cgi and under Comment type "Request password for NA-MIC Sandbox". '''It says NA-MIC Sandbox since Slicer 3 is part of NA-MIC activity.''' Once you have access to write to SVN, you can work with repository using the following commands: |
To update repository: | To update repository: |
Revision as of 15:54, 4 January 2007
Home < Slicer3:Contributing codes to Slicer3Contents
Objective
The goal of this page is to give quick insturction to download Slier3 from Subversion Control (SVN) server, and contribute codes by committing codes back to SVN.
How to obtain Slicer 3 codes from SVN
The Slicer3 svn repository sits in a server at Brigham and Women's Hospital in Boston. You can checkout codes by:
svn co http://www.na-mic.org:8000/svn/Slicer3/trunk Slicer3
You don't need to obtain an account if you don't commit codes back to the sever, but we enthusiastically invite you to do so.
How to commit codes
First, fill the form at https://www.kitware.com/Admin/SendPassword.cgi and under Comment type "Request password for NA-MIC Sandbox". It says NA-MIC Sandbox since Slicer 3 is part of NA-MIC activity. Once you have access to write to SVN, you can work with repository using the following commands:
To update repository:
svn update
To check current state of your edits:
svn status
To check the current state compared to the repository:
svn -u status
To add new file:
svn add filename
followed by (very important):
svn commit -m"ENH: Adding a new file" filename
To remove file:
svn remove filename
To rename file:
svn move oldname newname
If the update results in conflict, fix the file first before commiting it.
Once you have fixed the file:
svn resolved <filename>
GUI tools for eash SVN handling
It is handy to use GUI tool for SVN. I particulary like a cross-platform GUI tool called http://rapidsvn.tigris.org/.