diff options
| author | Tom Rini <trini@konsulko.com> | 2026-01-20 14:11:43 -0600 |
|---|---|---|
| committer | Heinrich Schuchardt <heinrich.schuchardt@canonical.com> | 2026-01-28 21:12:04 +0100 |
| commit | 5f6776883c66172cf784bc0ced2fbe3c1018ba9b (patch) | |
| tree | 9b214cb18ae56cffea21c161fde6c61464ffa87a /doc/develop | |
| parent | 86455a8e4b11f957bb5af4f75762ce8d599309f7 (diff) | |
doc: develop: process: Move the existing block about patch application
We have a long block about the expectations and feedback about a patch
applying, or not, as part of the Custodian workflow. Move this to the
Custodians section from the Workflow of a custodian section.
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Diffstat (limited to 'doc/develop')
| -rw-r--r-- | doc/develop/process.rst | 22 |
1 files changed, 13 insertions, 9 deletions
diff --git a/doc/develop/process.rst b/doc/develop/process.rst index 4bfbf0eb9c6..81e1aa7e34d 100644 --- a/doc/develop/process.rst +++ b/doc/develop/process.rst @@ -143,6 +143,17 @@ 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. +Another form of feedback is about applying the patch itself to the +source tree. The custodian is expected to put in a "best effort" if a +patch does not apply cleanly, but can be made to apply still. It is up +to the custodian to decide how recent of a commit the patch must be +against. It is acceptable to request patches against the last officially +released version of U-Boot or newer. Of course a custodian can also +accept patches against older code. It can be difficult to find the +correct balance between putting too much work on the custodian or too +much work on an individual submitting a patch when something does not +apply cleanly. + Review Process, Git Tags ------------------------ @@ -236,15 +247,8 @@ like this: #. U-Boot Philosophy, as documented in :doc:`designprinciples`. - #. Applies cleanly to the source tree. The custodian is expected to put in - a "best effort" if a patch does not apply cleanly, but can be made to apply - still. It is up to the custodian to decide how recent of a commit the - patch must be against. It is acceptable to request patches against the - last officially released version of U-Boot or newer. Of course a - custodian can also accept patches against older code. It can be - difficult to find the correct balance between putting too much work on - the custodian or too much work on an individual submitting a patch when - something does not apply cleanly. + #. Can be applied easily to the source tree, as documented in the + :ref:`custodians` section. #. Passes :doc:`ci_testing` as this checks for new warnings and other issues. |