This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| lirec:version_control_guide [2009-02-04 15:54] – davegriffiths | lirec:version_control_guide [2009-02-04 15:55] – davegriffiths |
|---|
| I've set up the lirec svn repository with a dummy project called 'sandbox' that you can play with and break to your heart's content. This guide is written for the commandline version of svn, and heavily biased towards linux. If you prefer buttons to press, read through this document anyway as the concepts are the same, and then have a look at [[http://tortoisesvn.tigris.org/|Tortoise SVN]] or [[http://subclipse.tigris.org/|SubClipse]] if you use Eclipse or [[http://www.visualsvn.com/|VisualSVN]] if you use VisualStudio. [TODO - update this with a guide for using these systems.] | I've set up the lirec svn repository with a dummy project called 'sandbox' that you can play with and break to your heart's content. This guide is written for the commandline version of svn, and heavily biased towards linux. If you prefer buttons to press, read through this document anyway as the concepts are the same, and then have a look at [[http://tortoisesvn.tigris.org/|Tortoise SVN]] or [[http://subclipse.tigris.org/|SubClipse]] if you use Eclipse or [[http://www.visualsvn.com/|VisualSVN]] if you use VisualStudio. [TODO - update this with a guide for using these systems.] |
| |
| Firstly svn likes to know what editor you like to use so it can launch it to add comments for your code commits. Put this in your .bashrc: | Firstly svn likes to know what editor you like to use so it can launch it to add comments for your code commits. Put this environment variable in your .bashrc: |
| |
| <code>export EDITOR=vi</code> | <code>export EDITOR=vi</code> |
| |
| Or the equivalent in windows [TODO]. | Or do the equivalent in windows [TODO]. |
| |
| ====Getting the code==== | ====Getting the code==== |
81.188.78.24