From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: dwmw2@infradead.org, netdev@vger.kernel.org
Subject: Re: [iproute2 patch]: Add 'ip tuntap' facility for managing tun/tap devices
Date: Wed, 27 May 2009 13:44:53 -0700 (PDT) [thread overview]
Message-ID: <20090527.134453.120974750.davem@davemloft.net> (raw)
In-Reply-To: <20090527100647.06f07e1f@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 27 May 2009 10:06:47 -0700
> Well if the kernel interface existed for years, there were obviously other
> tools using it. Why do you have to cram that into iproute2?
Because iproute2 is what we want everyone to use perhaps?!?!?!?
Stephen, STOP THIS PASSIVE AGGRESSIVE CRAP.
It's not becoming, and it's just delaying making iproute2 more
useful by supporting tuntap devices properly.
next prev parent reply other threads:[~2009-05-27 20:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 10:32 tun: add tun_flags, owner, group attributes in sysfs David Woodhouse
2009-05-04 10:36 ` Michael Tokarev
2009-05-05 22:18 ` David Woodhouse
2009-05-04 10:42 ` [iproute2 patch]: Add 'ip tuntap' facility for managing tun/tap devices David Woodhouse
2009-05-04 14:38 ` Stephen Hemminger
2009-05-04 14:49 ` David Woodhouse
2009-05-27 16:32 ` David Woodhouse
2009-05-27 16:38 ` Stephen Hemminger
2009-05-27 16:49 ` David Woodhouse
2009-05-27 17:06 ` Stephen Hemminger
2009-05-27 20:44 ` David Miller [this message]
2009-05-27 20:43 ` David Miller
2009-05-28 4:58 ` Stephen Hemminger
2009-05-28 8:12 ` David Woodhouse
2009-06-13 8:55 ` David Woodhouse
2009-07-20 23:44 ` David Woodhouse
2009-05-04 14:47 ` tun: add tun_flags, owner, group attributes in sysfs Stephen Hemminger
2009-05-04 14:58 ` David Woodhouse
2009-05-09 20:27 ` David Miller
2009-05-09 22:27 ` David Woodhouse
2009-05-09 22:55 ` David Woodhouse
2009-05-09 22:56 ` David Miller
2009-05-10 5:54 ` David Miller
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=20090527.134453.120974750.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 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).