From: Stefano Brivio <sbrivio@redhat.com>
To: Phil Sutter <phil@nwl.cc>, Pablo Neira Ayuso <pablo@netfilter.org>
Cc: "Laura García Liébana" <nevola@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] tests: shell: Drop redefinition of DIFF variable
Date: Mon, 15 Jun 2020 16:36:18 +0200 [thread overview]
Message-ID: <20200615163618.77b209d5@elisabeth> (raw)
In-Reply-To: <20200615132134.GK23632@orbyte.nwl.cc>
On Mon, 15 Jun 2020 15:21:34 +0200
Phil Sutter <phil@nwl.cc> wrote:
> On Mon, Jun 15, 2020 at 02:40:55PM +0200, Stefano Brivio wrote:
> >
> > [...]
> >
> > Commit 7d93e2c2fbc7 (which makes it "configurable") is from March 2018.
>
> I think you're misinterpreting that commit regarding an attempt at
> making diff binary configurable.
>
> [...]
>
> > [...]
> >
> > # grep DIFF=\" nftables/tests/shell/run-tests.sh
> > DIFF="diff -y"
>
> This is no guaranteed functionality. There's no comment or anything
> stating you could change the DIFF definition atop the script to
> customize diff behaviour.
But...
# Configuration
TESTDIR="./$(dirname $0)/"
RETURNCODE_SEPARATOR="_"
SRC_NFT="$(dirname $0)/../../src/nft"
+POSITIVE_RET=0
+DIFF=$(which diff)
:) well, now that you tell me, I can guess that "# Configuration" only
applied to the original parts, and the rest was added there simply
because there were no other "sections".
> [...]
>
> As said, the quotes are there to cover the expected 'which' output, no
> more and no less. Supporting user-defined diff-command (or custom
> options) is new functionality IMO. I'm totally fine with that and merely
> want to point out we're not talking about fixing a bug here.
Okay, I see. I'll try to get back to that soon.
Pablo, I think you can drop this patch.
--
Stefano
prev parent reply other threads:[~2020-06-15 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 21:41 [PATCH nft] tests: shell: Drop redefinition of DIFF variable Stefano Brivio
2020-06-15 9:00 ` Phil Sutter
2020-06-15 10:18 ` Stefano Brivio
2020-06-15 11:54 ` Phil Sutter
2020-06-15 12:40 ` Stefano Brivio
2020-06-15 13:21 ` Phil Sutter
2020-06-15 14:36 ` Stefano Brivio [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=20200615163618.77b209d5@elisabeth \
--to=sbrivio@redhat.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=nevola@gmail.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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