Subversion day to day - Revision history

Genie-user: /* Checkout */

2006-09-06T14:17:29Z

Checkout

2006-02-10T13:46:26Z

2006-02-10T13:45:13Z

Test

2006-02-09T23:39:02Z

Subversion's Working Cycle

2006-02-08T17:51:56Z

2006-02-08T17:42:33Z

Test

2006-02-08T17:40:30Z

2006-02-07T16:20:44Z

2006-02-07T16:19:57Z

2006-02-07T16:19:22Z

@@ Line 25: / Line 25: @@
 <pre>
-svn checkout http://source.ggy.bris.ac.uk/subversion/myproject/trunk --user-name mylogin workingcopy
+svn checkout http://source.ggy.bris.ac.uk/subversion/myproject/trunk --username mylogin workingcopy
 </pre>

@@ Line 10: / Line 10: @@
 <pre>
 # checkout/update
 # test
 # edit (add/delete/copy/move)

@@ Line 46: / Line 46: @@
 ===Test===
-The tests that you make will be particular to your project.  Experience has shown that having your test suite fully automated in incorporated directly into you build system (e.g. your set of makefiles) pays dividends.  The time spent setting this up is repaid many times over in the time saved when a bug inevitably finds its way into the code.  Please contact an [[Help:Administrators|administrator]] if you would like to discuss setting up your test suite.
+The tests that you make will be particular to your project.  Experience has shown that having your test suite fully automated and incorporated directly into you build system (e.g. your set of makefiles) pays dividends.  The time spent setting this up is repaid many times over in the time saved when a bug inevitably finds its way into the code.  Please contact an [[Help:Administrators|administrator]] if you would like to discuss setting up your test suite.
 ===Edit===

@@ Line 10: / Line 10: @@
 <pre>
 # checkout/update
 # test
 # edit (add/delete/copy/move)

← Older revision		Revision as of 17:51, 8 February 2006
Line 1:		Line 1:
		+	[[Category:Version Control]]
		+	[[Category:Subversion]]
		+
	If you are using a graphical user interface to Subversion (such as Tortoise SVN), all the commands described here should be available from the menus.		If you are using a graphical user interface to Subversion (such as Tortoise SVN), all the commands described here should be available from the menus.

← Older revision		Revision as of 17:40, 8 February 2006
Line 1:		Line 1:
		+	If you are using a graphical user interface to Subversion (such as Tortoise SVN), all the commands described here should be available from the menus.
		+
	==Subversion's Working Cycle==		==Subversion's Working Cycle==

@@ Line 94: / Line 94: @@
 ===Commit===
-Now that you have made and tested your changes, it is time to create a new version of the repository.  An invaluable feature Subversion provides is the ability to record a log message at this time.  Later you, and your project partners, will be able to look back and say, "Oh THAT's why we made those changes", rather than a lot of head scratching, quizical looks culminating in a resigned "I think we'd better start again.."
+Now that you have made and tested your changes, it is time to create a new version of the repository.  An invaluable feature Subversion provides is the ability to record a log message at this time.  Later you, and your project partners, will be able to look back and say, "Oh THAT's why we made those changes", rather than a lot of head scratching and quizical looks culminating in a resigned "I think we'd better start again.."
 <pre>

@@ Line 7: / Line 7: @@
 # test
 # edit (add/delete/copy/move)
-# test again
+# test
 # commit
 </pre>
@@ Line 88: / Line 88: @@
 will recover a pristine copy of ''myfile'' exactly how it was before your changes.
-===Test===
+===Test Again===
 You will definitely want to make sure that the changes you made are working as you had hoped.  Just before you commit your changes is the time to be ''certain'' that everything is tickety-boo.  By doing this, you are likely to save yourself a whole load of time and heart-ache later on.