Introduction to Subversion - Revision history

Jprenaud: /* Why Subversion? */

2007-03-09T21:53:16Z

Why Subversion?

Jprenaud: /* More about Subversion */

2006-03-01T13:25:02Z

More about Subversion

Jprenaud: /* More about Subversion */

2006-03-01T13:09:05Z

More about Subversion

Jprenaud at 13:41, 10 February 2006

2006-02-10T13:41:14Z

Jprenaud at 13:39, 10 February 2006

2006-02-10T13:39:39Z

Jprenaud at 13:36, 10 February 2006

2006-02-10T13:36:50Z

Jprenaud at 00:13, 10 February 2006

2006-02-10T00:13:50Z

Jprenaud at 00:13, 10 February 2006

2006-02-10T00:13:20Z

Jprenaud at 23:57, 9 February 2006

2006-02-09T23:57:10Z

Jprenaud at 23:42, 9 February 2006

2006-02-09T23:42:25Z

@@ Line 5: / Line 5: @@
 ==Why Subversion?==
-Subversion is very similar to the better know [http://www.nongnu.org/cvs CVS] system however, Subversion has several neat advantages over CVS:
+Subversion is very similar to the better known [http://www.nongnu.org/cvs CVS] system however, Subversion has several neat advantages over CVS:
 * files and directory can be renamed and keep their history throughout the life of the project.
 * commits are atomic, i.e. when you sent a lot of changes to the server, the "commit" is either successful or not. For instance, if the network connection is lost halfway through the transaction, the whole commit fail and the repository is not affected. It also means that you can identify very easily all files changed during a commit.

← Older revision		Revision as of 13:25, 1 March 2006
Line 28:		Line 28:
	To find out more about Subversion, we suggest you play with the <tt>myproject</tt> example for a while and look at some more specific [[Subversion day to day\|Subversion concepts]]. The [[Subversion links\|links section]] contains links to documentation and Subversion clients that you can download to your computer.		To find out more about Subversion, we suggest you play with the <tt>myproject</tt> example for a while and look at some more specific [[Subversion day to day\|Subversion concepts]]. The [[Subversion links\|links section]] contains links to documentation and Subversion clients that you can download to your computer.

−	[[Media:subversion~~-intro~~.pdf]]	+	The slides from the Subversion workshop are also available [ [[Media:Introduction-to-subversion.pdf\| pdf]] ]. They contain an introduction to version control, the Subversion terminology and an quick overview of some of the clients.

← Older revision		Revision as of 13:09, 1 March 2006
Line 27:		Line 27:
	==More about Subversion==		==More about Subversion==
	To find out more about Subversion, we suggest you play with the <tt>myproject</tt> example for a while and look at some more specific [[Subversion day to day\|Subversion concepts]]. The [[Subversion links\|links section]] contains links to documentation and Subversion clients that you can download to your computer.		To find out more about Subversion, we suggest you play with the <tt>myproject</tt> example for a while and look at some more specific [[Subversion day to day\|Subversion concepts]]. The [[Subversion links\|links section]] contains links to documentation and Subversion clients that you can download to your computer.
		+
		+	[[Media:subversion-intro.pdf]]

@@ Line 5: / Line 5: @@
 ==Why Subversion?==
-Subversion is very similar to the better know [http://www.nongnu.org/cvs/ | CVS] system however, Subversion has several neat advantages over CVS:
+Subversion is very similar to the better know [http://www.nongnu.org/cvs CVS] system however, Subversion has several neat advantages over CVS:
 * files and directory can be renamed and keep their history throughout the life of the project.
 * commits are atomic, i.e. when you sent a lot of changes to the server, the "commit" is either successful or not. For instance, if the network connection is lost halfway through the transaction, the whole commit fail and the repository is not affected. It also means that you can identify very easily all files changed during a commit.

@@ Line 2: / Line 2: @@
 [[Category:Subversion]]
-Subversion is an open-source [[Version control]] system.
+Subversion is an open-source centralised [[Version control]] system. The web page for the Subversion project is http://subversion.tigris.org.
 ==Why Subversion?==
 Subversion is very similar to the better know [http://www.nongnu.org/cvs/ | CVS] system however, Subversion has several neat advantages over CVS:
 * files and directory can be renamed and keep their history throughout the life of the project.
-* commits are atomic, i.e. when you sent a lot of changes to the server, the "commit" is either successful or not. For instance, if the network connection is lost halfway through the transaction, the whole commit fail and the repository is not affected. It also mean that you can identify very easily all files changed during a commit.
+* commits are atomic, i.e. when you sent a lot of changes to the server, the "commit" is either successful or not. For instance, if the network connection is lost halfway through the transaction, the whole commit fail and the repository is not affected. It also means that you can identify very easily all files changed during a commit.
-* a wider choice of access methods is provided, in particular webdav allows easy access via a web browser.
+* a wider choice of access methods is provided, in particular ''webdav'' allows easy access via a web browser.
-* support for binary files, i.e. Word documents or Excel spreadsheets can be versionned via Subversion.
+* support for binary files, i.e. Word documents or Excel spreadsheets can be versioned via Subversion.
 This is why we chose to install Subversion as the version control system on <tt>[[Subversion server | source]]</tt>. Subversion is actually being developed as a modern successor for CVS and it makes sense to standardise on a more modern technology. Current CVS user will become familiar very quickly with Subversion and new users should not find it any harder to learn.

@@ Line 5: / Line 5: @@
 ==Why Subversion?==
-It is very similar to the better know [http://www.nongnu.org/cvs/ | CVS] system however, Subversion has several neat advantages over CVS:
+Subversion is very similar to the better know [http://www.nongnu.org/cvs/ | CVS] system however, Subversion has several neat advantages over CVS:
 * files and directory can be renamed and keep their history throughout the life of the project.
 * commits are atomic, i.e. when you sent a lot of changes to the server, the "commit" is either successful or not. For instance, if the network connection is lost halfway through the transaction, the whole commit fail and the repository is not affected. It also mean that you can identify very easily all files changed during a commit.
@@ Line 11: / Line 11: @@
 * support for binary files, i.e. Word documents or Excel spreadsheets can be versionned via Subversion.
-This is why we chose to install Subversion as the version control system on <tt>[[Subversion server | source]]</tt>. Subversion is actually being developed as a modern successor for CVS and it makes sense to standardize on a more modern technology.
+This is why we chose to install Subversion as the version control system on <tt>[[Subversion server | source]]</tt>. Subversion is actually being developed as a modern successor for CVS and it makes sense to standardise on a more modern technology. Current CVS user will become familiar very quickly with Subversion and new users should not find it any harder to learn.
-==Example: <tt>myproject</tt>==
+==<tt>source</tt>: our Subversion server==
-<tt>myproject</tt> is an example repository that is setup on <tt>[[Subversion server | source]]</tt> to test subversion. You can access it with a web browser at the URL http://source.ggy.bris.ac.uk/websvn using your login and password. If you do not have an account on <tt>[[Subversion server | source]]</tt>, use the combination guest/imaguest. Naviguate to the <tt>trunk</tt> directory and look at the files, the log and other links to get familiar with the interface.
+<tt>source</tt> is a Subversion server that is available for the geographers at Bristol University who are interested in using [[Version Control]] for their project. Your projects can be hosted on <tt>source</tt> in the Subversion system and we can give login to your collaborators so that they can access your code from anywhere with an Internet connection. The access control is very good and it is easy to lock some part of your project to a limited subset of developers for instance.
-If you have downloaded a [[Subversion links|subversion client]], you can use <tt>myproject</tt> as a test repository and send your own changes. To do this, use the URL http://source.ggy.bris.ac.uk/subversion/myproject and checkout <<t>myproject</tt>. You can then edit the files in your working copy and send the changes back to the server by "commiting" your changes.
+[[ Subversion server|More information]] about <tt>source</tt>.

@@ Line 15: / Line 15: @@
 ==Example: <tt>myproject</tt>==
-<tt>myproject</tt> is an example repository. You can access it at the URL http://source.ggy.bris.ac.uk/websvn using your login and password. If you do not have an account on <tt>[[Subversion server | source]]</tt>, use the combination guest/imaguest. Naviguate to the <tt>trunk</tt> directory and look at the files and their history.
+<tt>myproject</tt> is an example repository that is setup on <tt>[[Subversion server | source]]</tt> to test subversion. You can access it with a web browser at the URL http://source.ggy.bris.ac.uk/websvn using your login and password. If you do not have an account on <tt>[[Subversion server | source]]</tt>, use the combination guest/imaguest. Naviguate to the <tt>trunk</tt> directory and look at the files, the log and other links to get familiar with the interface..
-If you have downloaded a subversion client, you can use <tt>myproject</tt> as a test repository and send your own changes. To do this, use the URL http://source.ggy.bris.ac.uk/subversion/myproject. CHeckout
+If you have downloaded a [[Subversion links|subversion client]], you can use <tt>myproject</tt> as a test repository and send your own changes. To do this, use the URL http://source.ggy.bris.ac.uk/subversion/myproject and checkout <<t>myproject</tt>. You can then edit the files in your working copy and send the changes back to the server by "commiting" your changes.