Changes between Initial Version and Version 1 of UfoRevisionControl

Timestamp:

Jan 31, 2011, 7:33:09 PM (14 years ago)

Author:

Suren A. Chilingaryan

Comment:

--

UfoRevisionControl

@@ +1 @@
+= Repositories =
+
+There was some problems with integration of GIT repositories into the
+Trac. Therefore, I decided to install bazaar as a revision
+control system: http://bazaar.canonical.com/en/. The good documentation on bazaar commands is available here:
+http://doc.bazaar.canonical.com/bzr.2.2/en/
+
+I have installed the main repository for framework development. It is
+accessible with following bazaar URL:
+{{{ 
+  bzr+ssh://user@ufo.kit.edu/framework 
+}}}
+
+You can create new branches with the following command. This branches will be writable by creator only, but accessible for
+everybody else. As well the branches will immediately appear in the Trac
+source browser.
+{{{
+  bzr init bzr+ssh://user@ufo.kit.edu/framework/branch1
+}}}
+
+
+After branch initialization you can create local repository. Just call
+'bzr init' in root of the source folder. Files can be added with 'bzr
+add' command and revision can be commited with 'bzr commit -m some_comment'.
+This will work with local repository on your desktop computer. To submit
+stable revision to the server, for public use, please issue:
+{{{
+  bzr push bzr+ssh://user@ufo.kit.edu/framework/branch1
+}}}
+
+Alternatively, it is possible to instruct bazaar to synchronize with the
+server after each commit. Just bind server with the following command:
+{{{
+  bzr bind bzr+ssh://user@ufo.kit.edu/framework/branch1
+}}}
+
+It is also possible to create a personal repository (for whatever
+reason). The access pattern will be the same: writable by creator and
+readable by everybody else. However, it will not automatically appear in
+Trac. The new repository should be first added through Trac
+configuration page. The command:
+{{{
+  bzr init-repo bzr+ssh://user@ufo.kit.edu/repo1/
+}}}
+Then, the branches can be created as usual:
+{{{
+  bzr init bzr+ssh://user@ufo.kit.edu/repo1/branch1
+}}}
+
+
+
+To get access, please, create a ticket specifying the desired login and attaching your public key.