| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20231118152232.787e9ea2@kernel.org> Date: Sat, 18 Nov 2023 15:22:32 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Andrew Lunn <andrew@...n.ch> Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com, corbet@....net, workflows@...r.kernel.org, linux-doc@...r.kernel.org Subject: Re: [PATCH net] docs: netdev: try to guide people on dealing with silence 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.
Powered by blists - more mailing lists