Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 5ddacc4d2e26b432edff2deddc3195a7d5b92f6e Author: Marek Lindner mareklindner@neomailbox.ch Date: Sat Dec 19 13:04:29 2009 +0000
doc: open-mesh/Contribute
5ddacc4d2e26b432edff2deddc3195a7d5b92f6e open-mesh/Contribute.textile | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/open-mesh/Contribute.textile b/open-mesh/Contribute.textile index 21ee871a..37eb88c1 100644 --- a/open-mesh/Contribute.textile +++ b/open-mesh/Contribute.textile @@ -58,10 +58,18 @@ access to people that want to get involved. If you intend to send us patches, please consider the following guidelines:
* Prefer small & digestible over long "all in one" patches. + * No MIME, no links, no compression, no attachments. Just plain text. + * Patches sent to the mailing list should include "PATCH" in the subject to make[[BR]] + it easier to distinguish between patches and discussion. * The mails subject will become the first line in the commit message. The body [[BR]] contains the longer patch description and the patch (unified format) itself. [[BR]] - Please also specify the target branch (e.g. [batman], [batctl], etc) at the [[BR]] + Please also specify the target branch (e.g. batman:, batctl:, etc) at the [[BR]] beginning of the subject line. See the [http://www.open-mesh.org/timeline timeline] for more examples. * Add a "Signed-off-by: Your Name <you @ example.com>" line to the commit [[BR]] message to make the ownership of the patch clear. + * Patches for B.A.T.M.A.N. Advanced need to follow the linux kernel coding style[[BR]] + closely (check it using checkpatch.pl) as well as the linux "how to submit pacthes"[[BR]] + guidelines (search for the term !SubmitPatches to find thourough documentation). + * An exemplary good submission you may want to look at can be found here:[[BR]] + https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2009-December/002033.html