From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Netfilter user mailing list <netfilter@vger.kernel.org>
Subject: Re: Formal submission of Xtables2
Date: Thu, 13 Dec 2012 16:16:15 +0100 [thread overview]
Message-ID: <20121213151615.GA6962@1984> (raw)
In-Reply-To: <alpine.LNX.2.01.1212131528410.1273@nerf07.vanv.qr>
On Thu, Dec 13, 2012 at 03:53:45PM +0100, Jan Engelhardt wrote:
[...]
> In my opinion, there is nothing wrong with keeping some concepts. A
> developer is not required to reevaluate and reinnovate every concept
> there has been just for the heck of it. (The old "evolution, not
> revolution" credo.) Throwing everything overboard generally does not
> turn out to work these days.
Nobody is going to throw everything overboard. Nftables is backward
compatible while providing a new framework, revolutions are never
backward compatible.
next prev parent reply other threads:[~2012-12-13 15:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 6:00 Formal submission of Xtables2 Jan Engelhardt
2012-12-13 11:00 ` Pablo Neira Ayuso
2012-12-13 11:36 ` Jan Engelhardt
2012-12-13 12:05 ` Pablo Neira Ayuso
2012-12-13 13:08 ` Jan Engelhardt
2012-12-13 14:28 ` Pablo Neira Ayuso
2012-12-13 14:53 ` Jan Engelhardt
2012-12-13 15:16 ` Pablo Neira Ayuso [this message]
2012-12-13 16:41 ` Jan Engelhardt
2012-12-13 17:25 ` Pablo Neira Ayuso
2012-12-13 18:19 ` Jan Engelhardt
2012-12-17 0:08 ` Pablo Neira Ayuso
2012-12-17 1:39 ` Jan Engelhardt
2012-12-17 9:53 ` Pablo Neira Ayuso
2012-12-17 10:12 ` Maciej Żenczykowski
2012-12-17 13:01 ` Jan Engelhardt
2012-12-17 14:30 ` Pablo Neira Ayuso
2012-12-17 20:51 ` Jan Engelhardt
2012-12-17 23:49 ` Jozsef Kadlecsik
2012-12-18 1:11 ` Jan Engelhardt
2012-12-18 1:27 ` David Miller
[not found] ` <20121214094141.GO2606@workstation>
2012-12-16 23:57 ` Pablo Neira Ayuso
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=20121213151615.GA6962@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).