workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
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 15:22:32 -0800	[thread overview]
Message-ID: <20231118152232.787e9ea2@kernel.org> (raw)
In-Reply-To: <dd172cac-f530-4874-a4e7-fc8d7676d708@lunn.ch>

On Sat, 18 Nov 2023 20:09:43 +0100 Andrew Lunn wrote:
> > +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.

Hm. The whole "On the other hand, due to".. felt a bit clunky from 
the start, maybe that's the problem? Is this better?

 Generally speaking, the patches get triaged quickly (in less than
 48h). But be patient, if your patch is active in patchwork (i.e. it's
 listed on the project's patch list) the chances it was missed are close to zero.
+
+The high volume of development on netdev makes reviewers move on
+from discussions relatively quickly. New comments and replies 
+are very unlikely to arrive after a week of silence. If patch is
+no longer active in patchwork and the thread went idle for more than
+a week - clarify the next steps and/or post the next version.

  reply	other threads:[~2023-11-18 23:22 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
2023-11-18 23:22   ` Jakub Kicinski [this message]
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=20231118152232.787e9ea2@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --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