From f6618b55582fe9c3a17b927ef0f72fdb39ca2639 Mon Sep 17 00:00:00 2001
From: rudolfkoenig <>
Date: Thu, 15 Feb 2007 08:27:13 +0000
Subject: [PATCH] Some commands for beginners added

git-svn-id: https://svn.fhem.de/fhem/trunk@20 2b470e98-0d58-463d-a4d8-8e2adae1ed80
---
 fhem/README.CVS | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/fhem/README.CVS b/fhem/README.CVS
index 293ece278..2e547eebb 100644
--- a/fhem/README.CVS
+++ b/fhem/README.CVS
@@ -26,3 +26,32 @@ If you wish to contribute to the project, then
   You can increase the counter for bugfixing. Dont forget to mention the 
   tagname in the HISTORY file. Tagging helps to remove more complex changes or
   to merge them in other releases/branches.
+
+
+Some useful CVS commands/flags for the beginner:
+
+
+# Get the newest stuff from the server and merge it into your changes.
+# Watch out for lines beginning with C (collisions), edit them  immediately
+# after check out, and look for ==== 
+# Without -d new directories won't be checked out
+cvs update -d . 
+
+# Before checking in, make sure you changed only what you intended:
+cvs diff filename
+
+# Add new file. "-kb" adds binary files. Forgetting -kb will cause
+# problems if somebody is checking out on a different OS (windows)
+# Note: it is complicated to rename files in CVS, so think twice about
+# filenames before adding them. e.g. do not use version names in them.
+cvs add [-kb] filename
+
+# Look at the change history
+cvs log <filename>
+
+# Commit changes. Set the EDITOR environment variable to use your editor.
+cvs commit .
+
+# Check which files were changed. Type ^C when it asks you to really release it.
+# (is there a more elegant way?)
+cvs release .