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.] Patch to add mesh_no_rebroadcast
Date: Sun, 17 May 2015 09:11:18 +0200 [thread overview]
Message-ID: <29831806.Occmqno74R@sven-edge> (raw)
In-Reply-To: <1823317.pnFH07jJni@sven-edge>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Sunday 17 May 2015 00:00:27 Sven Eckelmann wrote:
> On Saturday 16 May 2015 22:07:36 Ruben Wisniewski wrote:
> > Signed-off-by: Linus Lüssing <linus.luessing@web.de>
> > ---
>
> Why are you sending a patch from Linus? And this patch doesn't apply on
> current master or next.
Just to make it more clear: I think it is not a problem to pick up some old
patch from someone else when the original author has no problem with it. But
taking a patch from someone else and then without any additional information
claiming to be the author is a rather bad move.
It is even worse that the informative commit subject + message was dropped.
There is also no information what you've changed before your signed-off-by
(which is also missing).
Btw. here is the original patch and the discussion
http://thread.gmane.org/gmane.org.freifunk.batman/10503
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-17 7:11 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 [this message]
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
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=29831806.Occmqno74R@sven-edge \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.