From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFC] batman-adv: Use kernel-like folder structure
Date: Sun, 19 Apr 2015 19:49:00 +0200 [thread overview]
Message-ID: <20150419174900.GG2396@odroid> (raw)
In-Reply-To: <1429298961-13250-1-git-send-email-sven@narfation.org>
On Fri, Apr 17, 2015 at 09:29:21PM +0200, Sven Eckelmann wrote:
> The person submitting the patches to the Networking maintainer has to take each
> patch and move files around and add some files to make it work in the actual
> kernel tree. Having all files included and already in the correct kernel tree
> layout should make this a lot easier.
I like the idea. Was moving patches between in- and
out-of-kernel-tree batman-adv a few times, too and that'd
spare an sed call in the future :).
next prev parent reply other threads:[~2015-04-19 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 19:29 [B.A.T.M.A.N.] [RFC] batman-adv: Use kernel-like folder structure Sven Eckelmann
2015-04-19 17:49 ` Linus Lüssing [this message]
2015-04-20 3:44 ` Marek Lindner
2015-04-20 6:26 ` 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=20150419174900.GG2396@odroid \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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