From: "Puustinen, Ismo" <ismo.puustinen@intel.com>
To: "arturo.borrero.glez@gmail.com" <arturo.borrero.glez@gmail.com>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft 0/1] Proposal: include directories for rulesets
Date: Fri, 4 Mar 2016 13:29:59 +0000 [thread overview]
Message-ID: <1457098198.32348.13.camel@intel.com> (raw)
In-Reply-To: <CAOkSjBjPom6KFPLEae7=LWUd79LuqPvV5mfQrhy37HY-jALvYw@mail.gmail.com>
On Fri, 2016-03-04 at 10:57 +0100, Arturo Borrero Gonzalez wrote:
> Hi Ismo,
>
> I like the idea. What I'm wondering is if it worth having another
> directive like 'includedir' to be more explicit.
Sure, I'm fine with that approach too. If the project leadership
indicates that the include directory approach makes sense, I could do a
patch using the 'includedir' syntax too.
Ismo
prev parent reply other threads:[~2016-03-04 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 12:11 [PATCH nft 0/1] Proposal: include directories for rulesets Ismo Puustinen
2016-03-02 12:11 ` [PATCH nft 1/1] scanner: add support for include directories Ismo Puustinen
2016-03-04 9:57 ` [PATCH nft 0/1] Proposal: include directories for rulesets Arturo Borrero Gonzalez
2016-03-04 13:29 ` Puustinen, Ismo [this message]
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=1457098198.32348.13.camel@intel.com \
--to=ismo.puustinen@intel.com \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@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).