From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net] docs: netdev: try to guide people on dealing with silence
Date: Sat, 18 Nov 2023 20:09:43 +0100 [thread overview]
Message-ID: <dd172cac-f530-4874-a4e7-fc8d7676d708@lunn.ch> (raw)
In-Reply-To: <20231118172412.202605-1-kuba@kernel.org>
> +On the other hand, due to the volume of development discussions on netdev
> +are very unlikely to be reignited after a week of silence.
My English parse falls over on 'are', and wants to backtrack and try
alternatives.
Maybe:
On the other hand, due to the volume of development discussions on
netdev, after a week of silence further discussions are very unlikely
to occur without prompting.
Andrew
next prev parent reply other threads:[~2023-11-18 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 17:24 Jakub Kicinski
2023-11-18 19:09 ` Andrew Lunn [this message]
2023-11-18 23:22 ` Jakub Kicinski
2023-11-20 20:01 Jakub Kicinski
2023-11-20 20:13 ` Mark Brown
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=dd172cac-f530-4874-a4e7-fc8d7676d708@lunn.ch \
--to=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=workflows@vger.kernel.org \
/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