From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Štěpán Němec" <snemec@redhat.com>
Cc: netfilter-devel@vger.kernel.org, Phil Sutter <phil@nwl.cc>,
Jeremy Sowden <jeremy@azazel.net>
Subject: Re: [nft PATCH 1/2] main: fix nft --help output fallout from 719e4427
Date: Mon, 22 Feb 2021 14:52:39 +0100 [thread overview]
Message-ID: <20210222135239.GA28388@salvia> (raw)
In-Reply-To: <20210222120320.2252514-1-snemec@redhat.com>
On Mon, Feb 22, 2021 at 01:03:19PM +0100, Štěpán Němec wrote:
> Long options were missing the double dash.
Applied, thanks
prev parent reply other threads:[~2021-02-22 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 12:03 [nft PATCH 1/2] main: fix nft --help output fallout from 719e4427 Štěpán Němec
2021-02-22 12:03 ` [nft PATCH 2/2] doc: nft: fix some typos and formatting issues Štěpán Němec
2021-02-22 13:52 ` Pablo Neira Ayuso
2021-02-22 13:52 ` 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=20210222135239.GA28388@salvia \
--to=pablo@netfilter.org \
--cc=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=snemec@redhat.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).