Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit a3f5fd96a07332510fe48d0685832312da8859c1 Author: Marek Lindner mareklindner@neomailbox.ch Date: Mon Dec 21 13:28:58 2009 +0000

doc: open-mesh/Contribute

a3f5fd96a07332510fe48d0685832312da8859c1 open-mesh/Contribute.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/open-mesh/Contribute.textile b/open-mesh/Contribute.textile index b3b2475d..3dea4bd4 100644 --- a/open-mesh/Contribute.textile +++ b/open-mesh/Contribute.textile @@ -63,13 +63,13 @@ If you intend to send us patches, please consider the following guidelines: it easier to distinguish between patches and discussions. * The mail's 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. batctl, batman-adv, 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 patch [[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 (use checkpatch.pl to verify your patch) as well as the linux "how to [[BR]] - submit patches" guidelines (search for the term !SubmitPatches to find thourough[[BR]] + submit patches" guidelines (search for the term !SubmitPatches to find thorough[[BR]] 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