From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/7] batctl: Add command to create/destroy batman-adv interface
Date: Tue, 20 Sep 2016 16:24:18 +0200 [thread overview]
Message-ID: <20160920142418.GA7375@otheros> (raw)
In-Reply-To: <1468423822-28324-2-git-send-email-sven@narfation.org>
On Wed, Jul 13, 2016 at 05:30:17PM +0200, Sven Eckelmann wrote:
> The command "new" can be used to create a batman-adv interface without any
> interface attached. This is helpful when the interfaces should be
> configured independently of the first attached interface.
Like in the title of this mail, maybe naming the commands
"create" and "destroy" instead of "new"/"destroy"?
The former sounds slightly more antonymic to me.
next prev parent reply other threads:[~2016-09-20 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 15:29 [B.A.T.M.A.N.] [PATCH 0/7] batctl: rtnetlink interface manipulation Sven Eckelmann
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 1/7] batctl: Use rtnl to query list of softif devices Sven Eckelmann
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 2/7] batctl: Add command to create/destroy batman-adv interface Sven Eckelmann
2016-09-20 14:24 ` Linus Lüssing [this message]
2016-09-20 15:43 ` Sven Eckelmann
2016-09-21 5:59 ` jmh8
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 3/7] batctl: Use rtnl to add/remove interfaces Sven Eckelmann
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 4/7] batctl: Parse interface arguments relative to last parsed option Sven Eckelmann
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 5/7] batctl: Allow to disable automatic interface new/destroy Sven Eckelmann
2016-09-20 14:29 ` Linus Lüssing
2016-09-20 15:36 ` Sven Eckelmann
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 6/7] batctl: Move interface command to extra file Sven Eckelmann
2016-07-13 15:30 ` [B.A.T.M.A.N.] [PATCH 7/7] batctl: Move check_mesh_iface* to functions.c 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=20160920142418.GA7375@otheros \
--to=linus.luessing@c0d3.blue \
--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.