FHEM/fhem-mirror
2
0
Fork 0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-02-01 01:09:47 +00:00
Code Issues Releases Wiki Activity
47a811511e
fhem-mirror/fhem
History
klaus-schauer 47a811511e 10_EnOcean: # unifies teach procedures 
# profile actuator.01: readings corrected
# various optimizations 

git-svn-id: https://svn.fhem.de/fhem/trunk@8848 2b470e98-0d58-463d-a4d8-8e2adae1ed80
2015-06-28 07:39:56 +00:00
..
contrib 36_LevelSender.zip: added support for RFM69 2015-06-21 19:05:21 +00:00
demolog fhem.cfg.demo: demo new Plot Types (logProxy+cubic) 2015-01-24 08:53:38 +00:00
docs fhem.pl: add featurelevel + set magic (Forum #38276) 2015-06-22 18:24:59 +00:00
FHEM 10_EnOcean: # unifies teach procedures 2015-06-28 07:39:56 +00:00
log Reorg - Part 5 2012-09-18 13:10:51 +00:00
webfrontend THE SPLIT 2012-11-04 13:49:43 +00:00
www console.js: Filter dialog position by justme1968 (Forum #38553) 2015-06-27 05:42:11 +00:00
CHANGED CHANGED: updated 2015-06-26 14:00:02 +00:00
configDB.pm configDB.pm: add template.layout to migration 2015-02-12 22:04:09 +00:00
COPYING GPLv2 added 2012-11-11 10:07:37 +00:00
fhem.cfg preparing/cleaning fhem.cfg 2013-09-22 13:10:32 +00:00
fhem.cfg.demo fhem.cfg.demo: demo new Plot Types (logProxy+cubic) 2015-01-24 08:53:38 +00:00
fhem.pl 98_backup.pm: execute in the background if called from FHEMWEB to avoid double execution 2015-06-23 18:40:53 +00:00
HISTORY added: New modules 10_pilight_ctrl, 30_pilight_dimmer, 30_pilight_switch and 30_pilight_temp to support pilight (sending and receiving) 2015-04-25 18:20:34 +00:00
MAINTAINER.txt 32_yowsup.pm: added module 2015-06-15 18:30:37 +00:00
Makefile Makefile: bugfix in target "deb" 2015-02-05 20:12:50 +00:00
README_DEMO.txt 01_FHEMWEB.pm: fixing RSS 2015-01-11 17:50:56 +00:00
README.SVN Sourceforge address change 2013-06-14 09:36:07 +00:00

README.SVN 

The source of this project is hosted on sourceforge, if you wish you can get
the latest version with the following command:

  svn co https://svn.code.sf.net/p/fhem/code/trunk/fhem

If you wish to contribute to the project, then
- create a sourceforge account 
- send an email to the project manager to add you as developer to the project
  (right know this is r dot koenig at koeniglich dot de)
- check out the source
- if it is already checked out, it makes sense to do an update before
  implementing your changes:
   % svn update
- make your changes
- test if it is working (Really !!!)
- make an entry in the CHANGED file, giving your changes a "title".
- describe your changes in the file HISTORY, and dont forget to mention your
  name and the date of change
- it makes sense to do a "svn diff" before checking in the stuff with
  svn commit