How to write a patch - Versionsgeschichte

Krikan: Verlinkung auf abzulösenden Artikel FHEM Command Beispiele ersetzt

2019-05-03T07:02:22Z

Verlinkung auf abzulösenden Artikel FHEM Command Beispiele ersetzt

← Nächstältere Version		Version vom 3. Mai 2019, 09:02 Uhr
Zeile 14:		Zeile 14:

	Edit the relevant file. Implement only one change.		Edit the relevant file. Implement only one change.
	If you log something consider the right log level. See [[~~FHEM Command Beispiele~~]]		If you log something consider the right log level. See [[DevelopmentModuleIntro#Logging / Debugging]], [[DevelopmentModuleAPI#Log3]], [[verbose]]

	== Test Changes ==		== Test Changes ==

Krikan: fhem.de-Link korrigiert

2017-03-01T10:07:24Z

fhem.de-Link korrigiert

← Nächstältere Version		Version vom 1. März 2017, 12:07 Uhr
Zeile 9:		Zeile 9:
	== Find The Module Maintainer ==		== Find The Module Maintainer ==

	View the file [http://~~www.~~fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. There you find out who is maintaining a module and where you should submit the patch.		View the file [http://fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. There you find out who is maintaining a module and where you should submit the patch.

	== Make Changes ==		== Make Changes ==
Zeile 46:		Zeile 46:
	== Submit the Patch ==		== Submit the Patch ==

	Visit the forum as stated in the file [http://~~www.~~fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.		Visit the forum as stated in the file [http://fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.
	Write a short description what the patch does and attach the patch file.		Write a short description what the patch does and attach the patch file.

Krikan: /* Checkout Sourcecode */ -> Anpassung an neues Repository

2016-12-12T10:51:05Z

Checkout Sourcecode: -> Anpassung an neues Repository

← Nächstältere Version		Version vom 12. Dezember 2016, 12:51 Uhr
Zeile 5:		Zeile 5:
	First checkout the source code from the svn repository.		First checkout the source code from the svn repository.

	svn checkout ~~http~~://svn.~~code~~.~~sf.net/p~~/fhem/~~code~~/~~trunk~~ fhem-code		svn checkout https://svn.fhem.de/fhem/trunk/fhem fhem-code

	== Find The Module Maintainer ==		== Find The Module Maintainer ==

Krikan: Forenbeitrag verlinkt

2015-05-30T17:41:31Z

Forenbeitrag verlinkt

← Nächstältere Version		Version vom 30. Mai 2015, 19:41 Uhr
Zeile 48:		Zeile 48:
	Visit the forum as stated in the file [http://www.fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.		Visit the forum as stated in the file [http://www.fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.
	Write a short description what the patch does and attach the patch file.		Write a short description what the patch does and attach the patch file.

			== Links ==
			* {{Link2Forum\|Topic=37121\|Message=299366\|LinkText=How to develop}}

	[[Kategorie:Development]]		[[Kategorie:Development]]

Krikan: Direktverlinkung http://www.fhem.de/MAINTAINER.txt

2014-10-24T11:28:24Z

Direktverlinkung http://www.fhem.de/MAINTAINER.txt

← Nächstältere Version		Version vom 24. Oktober 2014, 13:28 Uhr
Zeile 9:		Zeile 9:
	== Find The Module Maintainer ==		== Find The Module Maintainer ==

	View the file ''fhem/MAINTAINER.txt''. There you find out who is maintaining a module and where you should submit the patch.		View the file [http://www.fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. There you find out who is maintaining a module and where you should submit the patch.

	== Make Changes ==		== Make Changes ==
Zeile 46:		Zeile 46:
	== Submit the Patch ==		== Submit the Patch ==

	Visit the forum as stated in the file ''fhem/MAINTAINER.txt''. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.		Visit the forum as stated in the file [http://www.fhem.de/MAINTAINER.txt ''fhem/MAINTAINER.txt'']. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.
	Write a short description what the patch does and attach the patch file.		Write a short description what the patch does and attach the patch file.

	[[Kategorie:Development]]		[[Kategorie:Development]]

Krikan: Hinweis kein TABs benutzen in denglisch eingefügt

2014-09-29T16:39:46Z

Hinweis kein TABs benutzen in denglisch eingefügt

← Nächstältere Version		Version vom 29. September 2014, 18:39 Uhr
Zeile 40:		Zeile 40:
	== Create A Patch File ==		== Create A Patch File ==

	SVN helps you to create a proper patch file. Name it properly.		SVN helps you to create a proper patch file. Name it properly. Please do not use tabs in the patch-file. Use blanks instead.

	svn diff > ~/fix_ugly_bug.patch		svn diff > ~/fix_ugly_bug.patch

Krikan: Kategorie Guideline gelöscht

2014-08-29T08:03:41Z

Kategorie Guideline gelöscht

← Nächstältere Version		Version vom 29. August 2014, 10:03 Uhr
Zeile 49:		Zeile 49:
	Write a short description what the patch does and attach the patch file.		Write a short description what the patch does and attach the patch file.

	[[Kategorie:Development~~]][[Kategorie:Guidelines~~]]		[[Kategorie:Development]]

Hschmitt: Info about logging

2014-05-16T14:47:28Z

Info about logging

← Nächstältere Version		Version vom 16. Mai 2014, 16:47 Uhr
Zeile 14:		Zeile 14:

	Edit the relevant file. Implement only one change.		Edit the relevant file. Implement only one change.
			If you log something consider the right log level. See [[FHEM Command Beispiele]]

	== Test Changes ==		== Test Changes ==

Hschmitt: Die Seite wurde neu angelegt: „This article covers the process to write a patch and submit it. == Checkout Sourcecode == First checkout the source code from the svn repository. svn check…“

2014-05-06T20:49:22Z

Die Seite wurde neu angelegt: „This article covers the process to write a patch and submit it. == Checkout Sourcecode == First checkout the source code from the svn repository. svn check…“

Neue Seite

This article covers the process to write a patch and submit it.

== Checkout Sourcecode ==

First checkout the source code from the svn repository.

svn checkout http://svn.code.sf.net/p/fhem/code/trunk fhem-code

== Find The Module Maintainer ==

View the file ''fhem/MAINTAINER.txt''. There you find out who is maintaining a module and where you should submit the patch.

== Make Changes ==

Edit the relevant file. Implement only one change.

== Test Changes ==

Deploy the change to your fhem installation and test whether it fixes the problem or whether the new feature works as expected.

== Document Your Changes ==

At the end of the file you find the documentation starting with a ''=pod'' line. Add documentation as html fragements to it.
More infos can be found at [[Guidelines_zur_Dokumentation]]

== Check Documentation ==

Run the script commandref_join.pl and look at the output. If it complains fix the documentation.

cd fhem
contrib/commandref_join.pl

== Check Whether The Sourcecode is up to date ==

Before creating the patch check whether your sourcecode is up to date.

svn update

== Create A Patch File ==

SVN helps you to create a proper patch file. Name it properly.

svn diff > ~/fix_ugly_bug.patch

== Submit the Patch ==

Visit the forum as stated in the file ''fhem/MAINTAINER.txt''. Start a new thread with the subject starting with a <nowiki>[patch]</nowiki> and give it a meaningful title.
Write a short description what the patch does and attach the patch file.

[[Kategorie:Development]][[Kategorie:Guidelines]]