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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 20 Nov 2023 20:13:19 +0000
From: Mark Brown <broonie@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
	pabeni@...hat.com, andrew@...n.ch, 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 Mon, Nov 20, 2023 at 12:01:09PM -0800, Jakub Kicinski wrote:

> +Emails saying just "ping" or "bump" are considered rude. If you can't figure
> +out the status of the patch from patchwork or where the discussion has
> +landed - describe your best guess and ask if it's correct. For example::

> +  I don't understand what the next steps are. Person X seems to be unhappy
> +  with A, should I do B and repost the patches?

This bit (modulo the reference to patchwork) feels like it's generically
good advice and could find a home in submitting-patches.rst or similar,
not that it isn't worth repeating here.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ