summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorPaul Barker <pbarker@konsulko.com>2020-11-23 18:02:14 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-11-24 09:07:27 +0000
commitbdb0e2e757c6dcbf36a1be0c5060af10f99a73de (patch)
tree72ad658e5117fa7c0b52e4059f87fc8184ae879e /documentation/dev-manual
parent715ad8daf9c2ffe652bdce3b90517ad1074dd2cd (diff)
downloadpoky-bdb0e2e757c6dcbf36a1be0c5060af10f99a73de.tar.gz
dev-manual-common-tasks: Update & move patchwork reference
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>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.rst23
1 files changed, 13 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst
index e2957f479a..d43205712d 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.rst
+++ b/documentation/dev-manual/dev-manual-common-tasks.rst
@@ -10688,16 +10688,6 @@ Other layers may have similar testing branches but there is no formal
10688requirement or standard for these so please check the documentation for the 10688requirement or standard for these so please check the documentation for the
10689layers you are contributing to. 10689layers you are contributing to.
10690 10690
10691.. note::
10692
10693 This system is imperfect and changes can sometimes get lost in the
10694 flow. Asking about the status of a patch or change is reasonable if
10695 the change has been idle for a while with no feedback. The Yocto
10696 Project does have plans to use
10697 `Patchwork <https://en.wikipedia.org/wiki/Patchwork_(software)>`__
10698 to track the status of patches and also to automatically preview
10699 patches.
10700
10701The following sections provide procedures for submitting a change. 10691The following sections provide procedures for submitting a change.
10702 10692
10703.. _pushing-a-change-upstream: 10693.. _pushing-a-change-upstream:
@@ -10992,6 +10982,19 @@ without using the scripts:
10992 command, see ``GIT-SEND-EMAIL(1)`` displayed using the 10982 command, see ``GIT-SEND-EMAIL(1)`` displayed using the
10993 ``man git-send-email`` command. 10983 ``man git-send-email`` command.
10994 10984
10985The Yocto Project uses a `Patchwork instance <https://patchwork.openembedded.org/>`__
10986to track the status of patches submitted to the various mailing lists and to
10987support automated patch testing. Each submitted patch is checked for common
10988mistakes and deviations from the expected patch format and submitters are
10989notified by patchtest if such mistakes are found. This process helps to
10990reduce the burden of patch review on maintainers.
10991
10992.. note::
10993
10994 This system is imperfect and changes can sometimes get lost in the flow.
10995 Asking about the status of a patch or change is reasonable if the change
10996 has been idle for a while with no feedback.
10997
10995Working With Licenses 10998Working With Licenses
10996===================== 10999=====================
10997 11000