]> git.ipfire.org Git - thirdparty/u-boot.git/commitdiff
doc: develop: process: Add note about asking for feedback
authorTom Rini <trini@konsulko.com>
Tue, 23 Sep 2025 17:54:29 +0000 (11:54 -0600)
committerHeinrich Schuchardt <heinrich.schuchardt@canonical.com>
Sat, 27 Sep 2025 07:19:20 +0000 (09:19 +0200)
It can be unclear to contributors what to do if they haven't gotten any
feedback on patches they have submitted. Add a sentence saying that if
they feel it's been too long without any comment, it's OK to reply
again.

Signed-off-by: Tom Rini <trini@konsulko.com>
doc/develop/process.rst

index 0c6fb31e87b97aae418abb1e3c8e72acc7b1cad8..4bfbf0eb9c63b6ab0140bc61783b8542696e89cf 100644 (file)
@@ -139,7 +139,9 @@ comments). Even a "I have no time now, will look into it later"
 message is better than nothing. Also, if there are remarks to a
 patch, these should leave no doubt if they were just comments and the
 patch will be accepted anyway, or if the patch should be
-reworked/resubmitted, or if it was rejected.
+reworked/resubmitted, or if it was rejected. However, if a submitter
+feels it has been too long since posting their patch and not received
+any feedback, it is OK to follow-up and ask.
 
 Review Process, Git Tags
 ------------------------