Commit 35b4b6d0 authored by Jakub Kicinski's avatar Jakub Kicinski

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: default avatarMartin Habets <habetsm.xilinx@gmail.com>
Link: https://lore.kernel.org/r/20230823154922.1162644-1-kuba@kernel.orgSigned-off-by: default avatarJakub Kicinski <kuba@kernel.org>
parent 5d21d0a6
...@@ -167,6 +167,8 @@ Asking the maintainer for status updates on your ...@@ -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 patch is a good way to ensure your patch is ignored or pushed to the
bottom of the priority list. bottom of the priority list.
.. _Changes requested:
Changes requested Changes requested
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~
...@@ -359,6 +361,10 @@ Make sure you address all the feedback in your new posting. Do not post a new ...@@ -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 version of the code if the discussion about the previous version is still
ongoing, unless directly instructed by a reviewer. 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 Testing
------- -------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment