FHEM/fhem-mirror
2
0
Fork 0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-02-01 07:19:24 +00:00
Code Issues Releases Wiki Activity
59a3c29427
fhem-mirror/fhem
History
borisneubert 59a3c29427 66_ECMD, 67_ECMDDevice: 
- if split is used, the strings at which the messages are split 
                are still part of the messages
              - no default attributes for requestSeparator and responseSeparator
              - input of raw data as perl-encoded string (for setting 
                attributes)
              - be more verbose and explicit at loglevel 5
              - documentation corrected and amended

git-svn-id: https://svn.fhem.de/fhem/trunk@12796 2b470e98-0d58-463d-a4d8-8e2adae1ed80
2016-12-17 15:17:38 +00:00
..
contrib fhem.html: survey.pl discontinued, svn repository changed 2016-12-16 18:03:32 +00:00
demolog
docs fhem.html: typo 2016-12-16 18:54:17 +00:00
FHEM 66_ECMD, 67_ECMDDevice: 2016-12-17 15:17:38 +00:00
log
webfrontend
www 33_readingsGroup.pm: allow automatic sorting in reverse 2016-12-14 17:16:09 +00:00
CHANGED 66_ECMD, 67_ECMDDevice: 2016-12-17 15:17:38 +00:00
configDB.pm configDB.pm: change devicename to 64 chars 2016-09-05 19:06:04 +00:00
COPYING
fhem.cfg
fhem.cfg.demo fhem.cfg.demo: avoid ugly error message when loading Weather if JSON.pm is not installed 2016-05-18 17:23:01 +00:00
fhem.pl 01_FHEMWEB.pm & co: Dump "Probably associated with" in the raw definition (Forum #60599) 2016-12-14 13:04:42 +00:00
HISTORY 98_Verkehrsinfo.pm:New module retrieves trafficinformation 2016-12-11 10:52:39 +00:00
MAINTAINER.txt fhemweb_datetime.js: bugfix parameter settings, now it is possible to define 'defaultTime:21:00' 2016-12-15 06:40:20 +00:00
Makefile
README_DEMO.txt
README.SVN README.SVN: update Svn hostname 2016-12-14 10:06:59 +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.fhem.de/fhem/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