diff options
| author | Tom Rini <[email protected]> | 2025-09-23 11:54:29 -0600 |
|---|---|---|
| committer | Heinrich Schuchardt <[email protected]> | 2025-09-27 09:19:20 +0200 |
| commit | 7b5e66a2b3a2501dcff077fcc26ea55d6c5fba6e (patch) | |
| tree | aeb13cf3f502157fb48d9b2f0ab2044578d6a334 /doc/develop/process.rst | |
| parent | 77493c488bafafe7b347f38cc3df7ad395f810e1 (diff) | |
doc: develop: process: Add note about asking for feedback
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 <[email protected]>
Diffstat (limited to 'doc/develop/process.rst')
| -rw-r--r-- | doc/develop/process.rst | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/develop/process.rst b/doc/develop/process.rst index 0c6fb31e87b..4bfbf0eb9c6 100644 --- a/doc/develop/process.rst +++ b/doc/develop/process.rst @@ -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 ------------------------ |