From: Phil Sutter <phil@nwl.cc>
To: "Štěpán Němec" <snemec@redhat.com>
Cc: netfilter-devel@vger.kernel.org, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH nft 1/3] tests: shell: README: copy edit
Date: Wed, 20 Oct 2021 17:04:02 +0200 [thread overview]
Message-ID: <20211020150402.GJ1668@orbyte.nwl.cc> (raw)
In-Reply-To: <20211020124512.490288-1-snemec@redhat.com>
Hi,
What you you mean with 'copy edit'? Please make subject line a bit more
comprehensible. Also, adding at least a single line of description is
mandatory, even if the subject speaks for itself.
The actual changes look good to me, though!
Thanks, Phil
next prev parent reply other threads:[~2021-10-20 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 12:45 [PATCH nft 1/3] tests: shell: README: copy edit Štěpán Němec
2021-10-20 12:45 ` [PATCH nft 2/3] tests: shell: README: $NFT does not have to be a path to a binary Štěpán Němec
2021-10-20 12:45 ` [PATCH nft 3/3] tests: shell: README: clarify test file name convention Štěpán Němec
2021-10-20 15:04 ` Phil Sutter [this message]
2021-10-21 8:30 ` [PATCH nft 1/3] tests: shell: README: copy edit Štěpán Němec
2021-10-21 10:26 ` Phil Sutter
2021-10-21 11:03 ` Štěpán Němec
2021-10-27 9:06 ` Pablo Neira Ayuso
2021-10-27 9:51 ` Štěpán Němec
2021-10-27 10:13 ` Pablo Neira Ayuso
2021-10-27 11:04 ` Štěpán Němec
2021-10-27 19:07 ` Pablo Neira Ayuso
2021-11-05 11:39 ` [PATCH nft v2 1/4] " Štěpán Němec
2021-11-05 11:39 ` [PATCH nft v2 2/4] tests: shell: README: $NFT does not have to be a path to a binary Štěpán Němec
2021-11-05 11:39 ` [PATCH nft v2 3/4] tests: shell: README: clarify test file name convention Štěpán Němec
2021-11-05 11:39 ` [PATCH nft v2 4/4] tests: shell: $NFT needs to be invoked unquoted Štěpán Němec
2021-11-05 13:22 ` [PATCH nft v2 1/4] tests: shell: README: copy edit Phil Sutter
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=20211020150402.GJ1668@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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).