FHEM/fhem-mirror
2
0
Fork 0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-03-03 10:46:53 +00:00
Code Issues Releases Wiki Activity

Some commands for beginners added

Browse Source 
git-svn-id: https://svn.fhem.de/fhem/trunk@20 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
rudolfkoenig 2007-02-15 08:27:13 +00:00
parent 55601f3b9b
commit f6618b5558
1 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
fhem/README.CVS
View File

@ -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 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 tagname in the HISTORY file. Tagging helps to remove more complex changes or
to merge them in other releases/branches. 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 .