Changeset 1800 in orxonox.OLD for orxonox/trunk/documentation/README

Timestamp:

Apr 12, 2004, 7:12:42 PM (21 years ago)

Author:

patrick

Message:

README: svn finished

File:

• orxonox/trunk/documentation/README (modified) (6 diffs)

orxonox/trunk/documentation/README

@@ -9 +9 @@
 
 
-1.Manifesto:
+1.Preface:
 ----------
 Orxonox is a open-source vertical scroller game programed
@@ -16 +16 @@
 become _the_ open-source vertical scrolle ever.
 
+2.Manifesto:
+------------
+1) Alien is a great film
+2) Guiness is the most delicious beer
 
-2.Overview:
----------
-1.Manifesto
-2.Overview
-3.Contributing To The Project
+to be continoued...
 
 
-3.Contributing To The project:
+3.Overview:
+---------
+1.Preface
+2.Manifesto
+3.Overview
+3.Contributing To The Project
+4.Howto C++ Programming
+5.Howto SVN
+
+
+4.Contributing To The project:
 ------------------------------
 People who want to help us working on orxonox are always
@@ -51 +61 @@
 
 
-Howto C++ Programming:
+5.Howto C++ Programming:
 ------------------------
 If you are new to c/c++ programming, this project is probably
@@ -61 +71 @@
 
 
-Howto SVN:
-----------
+6.Howto SVN:
+------------
 For a more complete guide about this topic read the documentation
 avaiable at subversion.tigris.org.
@@ -94 +104 @@
 svn add <filename>
 and to publish all your changes type
-svn commit
-which will open a text program to show you a list of changes that will
-be committed. Delete the line beginning with '--', this will put all 
-your changes to the orxonox server.
+svn commit --message "Corrected number of chees slices."
+svn commit will send all of your changs to the repository. When you 
+commit a change, you need to supply a log message, describing your 
+change. The message can also be read from a file:
+svn commit --file logmsg
 
 If you accidently make a change you like to revert, you just can do this
@@ -103 +114 @@
 svn revert <filename>
 
+To keep track about the work that is running on the project use the
+command: svn log. This will show you a bref summary of all changes.
+
+
+Most of the programmer will do their work on a branch. A Branch is
+a line of development that exists independently of another line, yet
+still shares a common history. A branch always begins life as a copy
+of something, and moves on trom there, generating its own history. Later
+the two versions will merge.
+
+If you are working on orxonox you will have your own branch in which you 
+will program, some sort of sand-box. If you finish your work on your 
+topic, it will be revised by us and merged with the trunk
+
+
+
+
+#EOF