2
0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-02-01 01:09:47 +00:00
fhem-mirror/fhem
mgehre 919f4c28f4 MAX: Improve log message about invalid reading
git-svn-id: https://svn.fhem.de/fhem/trunk@7531 2b470e98-0d58-463d-a4d8-8e2adae1ed80
2015-01-11 18:59:37 +00:00
..
contrib EBUS: Konfigurationsdateien verbessert 2015-01-11 18:58:04 +00:00
demolog fhem.cfg.demo: moved copyright notice for pictures 2015-01-11 12:12:27 +00:00
docs fhem.pl: Make the event-on-change threshold work with even-min-interval (Forum #30810) 2014-12-22 07:12:41 +00:00
FHEM MAX: Improve log message about invalid reading 2015-01-11 18:59:37 +00:00
log
webfrontend
www fhembwe:js: fix time widget (23 hours instead of 12) 2015-01-11 13:22:08 +00:00
CHANGED 09_CUL_FHTTK.pm: small update of documentation in order to simulate the same, removed unnecessary check of sensor code 2015-01-11 18:52:43 +00:00
configDB.pm configDB.pm: fixed: recover 2015-01-09 12:39:08 +00:00
COPYING
fhem.cfg
fhem.cfg.demo fhem.cfg.demo: add define -ignoreErr for RSS 2015-01-11 17:55:36 +00:00
fhem.pl fhem.pl: move getUniqueId from 99_Utils.pm to fhem.pl (Forum #31932) 2015-01-11 18:23:31 +00:00
HISTORY Milight: Add new modules 30_MilightBridge and 31_MilightDevice 2014-12-22 22:41:48 +00:00
MAINTAINER.txt 14_CUL_TCM97001.pm: Add 14_CUL_TCM97001.pm to receive TCM 97001 temperature sensor (Forum #<forum.fhem.de 28519>) 2015-01-07 15:13:59 +00:00
Makefile Makefile: replace FHEM/98_fheminfo.pm $release (Forum #28928) 2014-11-12 22:33:07 +00:00
README_DEMO.txt 01_FHEMWEB.pm: fixing RSS 2015-01-11 17:50:56 +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