public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Interested in contributing
Date: Tue, 27 Sep 2016 08:16:47 +0200	[thread overview]
Message-ID: <5290440.gSl3Dkmz5X@bentobox> (raw)
In-Reply-To: <20160926230741.GC6995@otheros>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Dienstag, 27. September 2016 01:07:41 CEST Linus Lüssing wrote:
> PS: Also something, if you might already have some experience with
> kernel code, would be to simply help in reviewing pending patches.
> Maybe not as exciting as contributing something new and fancy. But
> it doesn't help to send patchsets for new features if too many, prior
> patches are still pending. So reviewing actually helps a lot and
> might contribute even more than submitting something new and fancy.

You can find the current pending patches at
 https://patchwork.open-mesh.org/project/b.a.t.m.a.n./list/

The correct way to announce your review is to submit comments inline as reply 
to the original mail (can be found in patchwork as mbox for each patch). If no 
problems could be found then please announce this also. The correct way to do 
it is described in https://www.kernel.org/doc/Documentation/SubmittingPatches 
under 13, 11 and 12.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-09-27  6:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 16:47 [B.A.T.M.A.N.] Interested in contributing leftbydefault
2016-09-26 23:07 ` Linus Lüssing
2016-09-27  6:16   ` Sven Eckelmann [this message]
2016-09-28 11:27   ` leftbydefault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5290440.gSl3Dkmz5X@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox