From: "Štěpán Němec" <snemec@redhat.com>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH nft 1/3] tests: shell: README: copy edit
Date: Thu, 21 Oct 2021 13:03:23 +0200 [thread overview]
Message-ID: <20211021130323+0200.342006-snemec@redhat.com> (raw)
In-Reply-To: <20211021102644.GM1668@orbyte.nwl.cc>
On Thu, 21 Oct 2021 12:26:44 +0200
Phil Sutter wrote:
> Sorry for not checking the guideline but quoting advice I once received
> from the top of my head instead. Maybe I was incorrect and in obvious
> cases the description is optional. The relevant text in [2] at least
> doesn't explicitly state it is, while being pretty verbose about it
> regarding cover letters.
Does this mean that you retract your requirement? If not, could you
please make sure that you and the other maintainers are on the same page
about this, and document the requirement?
Regarding this patch series (if it is to be resent, in part or as a
whole): we've discussed the first patch so far; the other two patches
have no description, either. Do they need one? If so, could you provide
some suggestions? I can't think of anything sensible that isn't already
said in the subject, Fixes:, or the modified README text itself.
Thanks,
Štěpán
next prev parent reply other threads:[~2021-10-21 11:02 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 ` [PATCH nft 1/3] tests: shell: README: copy edit Phil Sutter
2021-10-21 8:30 ` Štěpán Němec
2021-10-21 10:26 ` Phil Sutter
2021-10-21 11:03 ` Štěpán Němec [this message]
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=20211021130323+0200.342006-snemec@redhat.com \
--to=snemec@redhat.com \
--cc=netfilter-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).