diff options
| author | Jakub Kicinski | 2023-08-23 08:49:22 -0700 |
|---|---|---|
| committer | Jakub Kicinski | 2023-08-24 11:25:38 -0700 |
| commit | 35b4b6d0c53a3872e846dbcda9074117efdc078a (patch) | |
| tree | e6d036752b19f47457ea74a885919cc24ad25ade | |
| parent | 5d21d0a65b573507bae774708199328b38dedfe6 (diff) | |
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 <habetsm.xilinx@gmail.com>
Link: https://lore.kernel.org/r/20230823154922.1162644-1-kuba@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
| -rw-r--r-- | Documentation/process/maintainer-netdev.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst index 2ab843cde830..c1c732e9748b 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 ------- |