From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Varsha Rao <rvarsha016@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] tests: files: Remove old tests for chain rename.
Date: Fri, 6 Oct 2017 14:42:58 +0200 [thread overview]
Message-ID: <20171006124258.GF4713@salvia> (raw)
In-Reply-To: <20171005080647.15713-2-rvarsha016@gmail.com>
On Thu, Oct 05, 2017 at 01:36:47PM +0530, Varsha Rao wrote:
> These tests are not required as new test cases are added in tests/shell
> file.
Also applied, thanks.
It would be great if you can go over those tests/files/ to get rid of
them. Just make a replacement that we can fit into tests/shell/
However, before doing so, you should have a look first that there is
no overlap with any existing test, we should avoid duplicates. I mean,
go over files under tests/shell/ and make sure what you add does not
exists already in the tree.
Thanks!
next prev parent reply other threads:[~2017-10-06 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 8:06 [PATCH nft v2] tests: shell: Add tests for chain rename Varsha Rao
2017-10-05 8:06 ` [PATCH nft] tests: files: Remove old " Varsha Rao
2017-10-06 12:42 ` Pablo Neira Ayuso [this message]
2017-10-06 12:41 ` [PATCH nft v2] tests: shell: Add " Pablo Neira Ayuso
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=20171006124258.GF4713@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rvarsha016@gmail.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).