From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Jan Engelhardt <jengelh@medozas.de>
Cc: "netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kaber@trash.net" <kaber@trash.net>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"Ylalehto Janne (Nokia-MS/Tampere)" <janne.ylalehto@nokia.com>
Subject: Re: [PATCH 0/1] netfilter: xt_condition: add condition target
Date: Thu, 12 Aug 2010 13:14:04 +0300 [thread overview]
Message-ID: <1281608044.4440.18.camel@powerslave> (raw)
In-Reply-To: <alpine.LSU.2.01.1008121202320.31027@obet.zrqbmnf.qr>
On Thu, 2010-08-12 at 12:10 +0200, ext Jan Engelhardt wrote:
> On Thursday 2010-08-12 08:37, Luciano Coelho wrote:
> >
> >One thing that came to my mind was whether it would make sense to
> >rename this match/target combo to "variable" instead of "condition".
> >To me it makes more sense to call it variable than condition, since
> >I have changed the value from boolean to u32. On the other hand, it
> >could become very confusing because it used to be called condition
> >in its xtables-addons days...
>
> To improve matters, POSIX has something called "condition variables".
> So oh well let's just leave it as-is :)
:D
Okay, let's keep it like this, I guess it would just complicate things
more if we change it.
--
Cheers,
Luca.
prev parent reply other threads:[~2010-08-12 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 6:37 [PATCH 0/1] netfilter: xt_condition: add condition target Luciano Coelho
2010-08-12 6:37 ` [PATCH 1/1] netfilter: xt_condition: add condition target support Luciano Coelho
2010-08-12 10:10 ` [PATCH 0/1] netfilter: xt_condition: add condition target Jan Engelhardt
2010-08-12 10:14 ` Luciano Coelho [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=1281608044.4440.18.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=janne.ylalehto@nokia.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sameo@linux.intel.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).