From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>
Subject: [libnftnl PATCH v3 0/2] Do not print unset value in xml file
Date: Mon, 2 Jun 2014 14:06:08 +0200 [thread overview]
Message-ID: <1401710770-23662-1-git-send-email-anarey@gmail.com> (raw)
In this version, I rename some variables, I fix writing errors in the patch
description and I fix wrong indentation.
[Change in v2:]
Hi,
After some advises of Arturo Borrero, I send a previous patch to
'Code refactoring to use nft_rule_expr_set_* functions' patch and v2 of
"Do not print unset values in xml" patch.
Ana Rey (2):
expr: log: Code refactoring to use nft_rule_expr_set_* functions
src: expr: log: Do not print unset values in xml.
src/expr/log.c | 93 ++++++++++++++++++++++++++++++++++------------------------
1 file changed, 54 insertions(+), 39 deletions(-)
--
2.0.0.rc2
next reply other threads:[~2014-06-02 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 12:06 Ana Rey [this message]
2014-06-02 12:06 ` [libnftnl PATCH v3 1/2] expr: log: Code refactoring to use nft_rule_expr_set_* functions Ana Rey
2014-06-02 12:33 ` Pablo Neira Ayuso
2014-06-02 12:06 ` [libnftnl PATCH v3 2/2] src: expr: log: Do not print unset values in xml Ana Rey
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=1401710770-23662-1-git-send-email-anarey@gmail.com \
--to=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;
as well as URLs for NNTP newsgroup(s).