mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-04-13 14:02:21 +02:00
Code Issues Packages Projects Releases Wiki Activity

dev-manual-common-tasks: Update & move patchwork reference

Browse Source 
Add a link to our patchwork instance and note how submitted patches are
checked for common mistakes. This note is moved to the section on
submitting patches via email as that is the place where most users will
run into patchwork/patchtest.

(From yocto-docs rev: 76506bc6125b551c5aa9c45f2b1e7b89e6bf6eae)

Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Paul Barker
2020-11-23 18:02:14 +00:00
committed by Richard Purdie
parent 715ad8daf9
commit bdb0e2e757
1 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
documentation/dev-manual/dev-manual-common-tasks.rst
View File

@@ -10688,16 +10688,6 @@ Other layers may have similar testing branches but there is no formal
requirement or standard for these so please check the documentation for the
layers you are contributing to.
.. note::
This system is imperfect and changes can sometimes get lost in the
flow. Asking about the status of a patch or change is reasonable if
the change has been idle for a while with no feedback. The Yocto
Project does have plans to use
`Patchwork <https://en.wikipedia.org/wiki/Patchwork_(software)>`__
to track the status of patches and also to automatically preview
patches.
The following sections provide procedures for submitting a change.
.. _pushing-a-change-upstream:
@@ -10992,6 +10982,19 @@ without using the scripts:
command, see ``GIT-SEND-EMAIL(1)`` displayed using the
``man git-send-email`` command.
The Yocto Project uses a `Patchwork instance <https://patchwork.openembedded.org/>`__
to track the status of patches submitted to the various mailing lists and to
support automated patch testing. Each submitted patch is checked for common
mistakes and deviations from the expected patch format and submitters are
notified by patchtest if such mistakes are found. This process helps to
reduce the burden of patch review on maintainers.
.. note::
This system is imperfect and changes can sometimes get lost in the flow.
Asking about the status of a patch or change is reasonable if the change
has been idle for a while with no feedback.
Working With Licenses
=====================