public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Patch to add mesh_no_rebroadcast
Date: Fri, 07 Aug 2015 02:25:22 +0200	[thread overview]
Message-ID: <2457781.aV3nu67AfV@prime> (raw)
In-Reply-To: <1438896208.1369.49.camel@nord-west.org>

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

Hi Bjoern,

there wasn't any activity on this patch (at least from our side), and there 
wasn't any reaction on Mareks suggestion to add more explanation to the patch.

If you want to get it adopted, please resend it (rebased on current master) 
with a proper commit message explaining what it does and why its useful - like 
we have for any other patch.

Thanks,
     Simon

On Thursday 06 August 2015 23:23:28 Bjoern Franke wrote:
> Hi,
> 
> > It might be a good idea to send an explanation with the patch to get
> > the
> > discussion started. What are the arguments in favor of this patch ? A
> > little
> > more than 'Patch to add mesh_no_rebroadcast' would be nice.
> 
> Is there any advance towards including this patch?
> 
> Regards
> Björn

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

  reply	other threads:[~2015-08-07  0:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16 20:07 [B.A.T.M.A.N.] Patch to add mesh_no_rebroadcast Ruben Wisniewski
2015-05-16 22:00 ` Sven Eckelmann
2015-05-17  7:11   ` Sven Eckelmann
2015-05-17  9:16     ` Ruben Wisniewski
2015-05-17 10:22       ` Sven Eckelmann
     [not found]   ` <20150517111208.61efc0ae@i3.local>
2015-05-17  9:18     ` Sven Eckelmann
2015-05-18  8:33 ` Simon Wunderlich
2015-05-18  9:41   ` Marek Lindner
2015-08-06 21:23     ` Bjoern Franke
2015-08-07  0:25       ` Simon Wunderlich [this message]
2016-07-27  2:17         ` Ruben Kelevra
2016-07-27  6:58           ` Sven Eckelmann

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=2457781.aV3nu67AfV@prime \
    --to=sw@simonwunderlich.de \
    --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