From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] Don't merge adjacent/overlapping ranges by default
Date: Wed, 10 Jan 2018 12:57:25 +0100 [thread overview]
Message-ID: <20180110115725.GO32305@orbyte.nwl.cc> (raw)
In-Reply-To: <20180110115100.z3hbazlk4w7lekga@salvia>
Hi Pablo,
On Wed, Jan 10, 2018 at 12:51:00PM +0100, Pablo Neira Ayuso wrote:
[...]
> I would disable this by default by now, no option.
>
> Then, revisit this later on to see if it's worth adding this, thanks!
Should I drop everything that's needed to make it optional or just
remove the option from src/main.c?
Cheers, Phil
next prev parent reply other threads:[~2018-01-10 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 10:42 [nft PATCH] Don't merge adjacent/overlapping ranges by default Phil Sutter
2018-01-10 11:51 ` Pablo Neira Ayuso
2018-01-10 11:57 ` Phil Sutter [this message]
2018-01-10 12:08 ` Pablo Neira Ayuso
2018-01-10 12:44 ` Phil Sutter
2018-01-10 14:16 ` Pablo Neira Ayuso
2018-01-10 20:32 ` [nft PATCH v2] Don't merge adjacent/overlapping ranges Phil Sutter
2018-01-11 12:08 ` 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=20180110115725.GO32305@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).