From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Vadim Kochan <vadim4j@gmail.com>, Jiri Benc <jbenc@redhat.com>
Cc: Brian Haley <brian.haley@hp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2 3/3] ip netns: Delete all netns
Date: Fri, 09 Jan 2015 15:24:02 +0100 [thread overview]
Message-ID: <54AFE482.7020108@6wind.com> (raw)
In-Reply-To: <CAMw6YJLx0O6dVnD2XcmF+qz+=m51TyZOqJWSYGKQ-XrMHP8z3w@mail.gmail.com>
Le 09/01/2015 10:54, Vadim Kochan a écrit :
> Ok,
>
> If I will re-work to use new option, would it be useful ? So it will look:
>
> $ ip -all netns del
> $ ip -all netns exec ip link
> $ ip -all netns exec ip route add ...
>
> Seems not so weird to me ?
What about making this new option only for the 'netns' subsystem?
Something like: 'ip netns -all exec'?
Regards,
Nicolas
next prev parent reply other threads:[~2015-01-09 14:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 11:04 [PATCH iproute2 0/3] ip netns: Run over all netns Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 1/3] lib: Exec func on each netns Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 2/3] ip netns: Allow exec " Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 3/3] ip netns: Delete all netns Vadim Kochan
2015-01-07 15:44 ` Brian Haley
2015-01-07 17:36 ` Vadim Kochan
2015-01-07 18:11 ` Vadim Kochan
2015-01-07 19:40 ` Brian Haley
2015-01-07 19:55 ` Vadim Kochan
2015-01-08 0:00 ` Cong Wang
2015-01-09 8:43 ` Jiri Benc
2015-01-09 9:54 ` Vadim Kochan
2015-01-09 14:24 ` Nicolas Dichtel [this message]
2015-01-08 0:04 ` [PATCH iproute2 0/3] ip netns: Run over " Cong Wang
2015-01-08 0:52 ` Vadim Kochan
2015-01-09 18:49 ` Cong Wang
2015-01-09 19:17 ` Vadim Kochan
2015-01-14 1:28 ` Stephen Hemminger
2015-01-14 16:13 ` Vadim Kochan
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=54AFE482.7020108@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=brian.haley@hp.com \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@gmail.com \
/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.