From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D4B52905 for ; Wed, 23 Aug 2023 15:49:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DD410C433C9; Wed, 23 Aug 2023 15:49:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1692805765; bh=NE42OlPzmRHlwFXCXXgi1f+Eb2OiCz1sD7zYgQ/OL2s=; h=From:To:Cc:Subject:Date:From; b=oVM6RklICxDkz/4elBAXRcH/fsjP8rqzNRWH2m7KbSNa+nVld7NxUXQVIm4Htxk8t qHvEWzLP7w7ptYMVlF8VGmJHACNspzxbUC+Vci07cna1WO7vlqqHMJaECc2lzUE0VY /UuHbHHlnNSeURoMuyDQRhg6LnidQ4EKv1PQ+2pQl3oZgi2NcpcDjkiygQ5/20sdL0 4cO4VDhxNYoFSLiYzNEfGop35aQ27D+4NnPSo3nRaTHRQ9Kp6xWN/DRbdYO3ur/fp0 Qz2pzlj+edBLD2aPxnyrhwLcjS5hiMTcHvxvcDdWe5jyzK3GWuErkSsMByU6920t8W dE9otp7fGttIA== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com, Jakub Kicinski Subject: [PATCH net-next] docs: netdev: recommend against --in-reply-to Date: Wed, 23 Aug 2023 08:49:22 -0700 Message-ID: <20230823154922.1162644-1-kuba@kernel.org> X-Mailer: git-send-email 2.41.0 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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. Signed-off-by: Jakub Kicinski --- Documentation/process/maintainer-netdev.rst | 6 ++++++ 1 file changed, 6 insertions(+) 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 ------- -- 2.41.0