From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ana Rey <anarey@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH v2 0/4] src: chain: Do not print unset values in json and xml
Date: Mon, 30 Jun 2014 14:38:35 +0200 [thread overview]
Message-ID: <20140630123835.GA14314@localhost> (raw)
In-Reply-To: <1404129008-29564-1-git-send-email-anarey@gmail.com>
On Mon, Jun 30, 2014 at 01:50:04PM +0200, Ana Rey wrote:
> In v1, this patchset contains the following patchs:
>
> "Ana Rey (6):
> src: chain: Free memory in the same function that is reserved
> src: chain: Use nft_rule_expr_set_* in the xml parsing code
> src: chain: add set, unset, get, parse and build payload
> implementation for use value
> src: chain: Do not print unset values in xml
> src: chain: Rename variables in nft_jansson_parse_chain functions
> src: chain: Do not print unser values in json
> "
>
> I resend a v2 version of four of these six patches. The main change is in
> "src: chain: Add all support of use attribute" patch
> [ in v1 was "src: chain: add set, unset, get, parse and build payload implementation for use value"]
Series applied, thanks Ana.
prev parent reply other threads:[~2014-06-30 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 11:50 [libnftnl PATCH v2 0/4] src: chain: Do not print unset values in json and xml Ana Rey
2014-06-30 11:50 ` [libnftnl PATCH v2 1/4] src: chain: Add all support of use attribute Ana Rey
2014-06-30 11:50 ` [libnftnl PATCH v2 2/4] src: chain: Do not print unset values in xml Ana Rey
2014-06-30 11:50 ` [libnftnl PATCH v2 3/4] src: chain: Rename variables in nft_jansson_parse_chain functions Ana Rey
2014-06-30 11:50 ` [libnftnl PATCH v2 4/4] src: chain: Do not print unser values in json Ana Rey
2014-06-30 12:38 ` Pablo Neira Ayuso [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=20140630123835.GA14314@localhost \
--to=pablo@netfilter.org \
--cc=anarey@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