From: Jakub Kicinski Date: Wed, 23 Aug 2023 15:49:22 +0000 (-0700) Subject: docs: netdev: recommend against --in-reply-to X-Git-Tag: v6.6.7~2079^2~32 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=35b4b6d0c53a3872e846dbcda9074117efdc078a;p=platform%2Fkernel%2Flinux-starfive.git docs: netdev: recommend against --in-reply-to It's somewhat unfortunate but with (my?) the current tooling if people post new versions of a set in reply to an old version managing the review queue gets difficult. So recommend against it. Reviewed-by: Martin Habets Link: https://lore.kernel.org/r/20230823154922.1162644-1-kuba@kernel.org Signed-off-by: Jakub Kicinski --- diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst index 2ab843c..c1c732e 100644 --- a/Documentation/process/maintainer-netdev.rst +++ b/Documentation/process/maintainer-netdev.rst @@ -167,6 +167,8 @@ Asking the maintainer for status updates on your patch is a good way to ensure your patch is ignored or pushed to the bottom of the priority list. +.. _Changes requested: + Changes requested ~~~~~~~~~~~~~~~~~ @@ -359,6 +361,10 @@ Make sure you address all the feedback in your new posting. Do not post a new version of the code if the discussion about the previous version is still ongoing, unless directly instructed by a reviewer. +The new version of patches should be posted as a separate thread, +not as a reply to the previous posting. Change log should include a link +to the previous posting (see :ref:`Changes requested`). + Testing -------