From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v3 iptables-nft 0/3] remove escape_quotes support
Date: Wed, 30 Nov 2022 20:37:02 +0100 [thread overview]
Message-ID: <Y4ew3gceeoLUpPb9@orbyte.nwl.cc> (raw)
In-Reply-To: <20221130093154.29004-1-fw@strlen.de>
On Wed, Nov 30, 2022 at 10:31:51AM +0100, Florian Westphal wrote:
> Changes since v3:
> - replace strcmp(s, "") with s[0], do not escape '
> - handle multiline expectations
Series applied after dropping the strcmp() changes and eliminating the
missed tick escaping.
Thanks!
prev parent reply other threads:[~2022-11-30 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 9:31 [PATCH v3 iptables-nft 0/3] remove escape_quotes support Florian Westphal
2022-11-30 9:31 ` [PATCH v3 iptables-nft 1/3] xlate: get rid of escape_quotes Florian Westphal
2022-11-30 12:35 ` Phil Sutter
2022-11-30 9:31 ` [PATCH v3 iptables-nft 2/3] extensions: change expected output for new format Florian Westphal
2022-11-30 9:31 ` [PATCH v3 iptables-nft 3/3] xlate-test: avoid shell entanglements Florian Westphal
2022-11-30 19:37 ` Phil Sutter [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=Y4ew3gceeoLUpPb9@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--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).