b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Ruben Wisniewski <ruben@freifunk-nrw.de>
Cc: 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: Sun, 17 May 2015 11:18:21 +0200	[thread overview]
Message-ID: <1931389.mJnGpBFORV@sven-edge> (raw)
In-Reply-To: <20150517111208.61efc0ae@i3.local>

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

Please don't drop the mailing list when replying (unless it is actually 
private conversation).

On Sunday 17 May 2015 11:12:08 Ruben Wisniewski wrote:
> schrieb Sven Eckelmann <sven@narfation.org>:
> > Why are you sending a patch from Linus?
> 
> Because Simon said to me to do so yesterday. :)

See my other mail with a more detailed explanation.


> > And this patch doesn't apply on current master or next.
> 
> We have this patch in our setup and it's applying to 2015.0.

But v2015.0 is not master or next. And since it is a new feature, I would 
guess it should be applied on master.

Kind regards,
	Sven

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

  parent reply	other threads:[~2015-05-17  9:18 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 [this message]
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
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=1931389.mJnGpBFORV@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=ruben@freifunk-nrw.de \
    /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;
as well as URLs for NNTP newsgroup(s).