From 82533714c148955d4d0bd08e82407c44b3a1f8ae Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Fri, 11 Aug 2023 11:41:04 +0200 Subject: contributor-guide: clarification about patchtest - Highlight that patchtest still needs improving - Fix reference to this tool (From yocto-docs rev: bdd5541b491729dcfa9e92a9acfc932c427a8ea0) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/contributor-guide/submit-change.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'documentation/contributor-guide') diff --git a/documentation/contributor-guide/submit-change.rst b/documentation/contributor-guide/submit-change.rst index 3fd2b049cf..6bee423bfb 100644 --- a/documentation/contributor-guide/submit-change.rst +++ b/documentation/contributor-guide/submit-change.rst @@ -43,7 +43,7 @@ mailing list approach off-putting and would prefer a web-based GUI. Since we don’t believe that can work for us, the project is aiming to ensure `patchwork `__ is available to help track patch status and also looking at how tooling can provide more feedback to users -about patch status. We are looking at tools such as ``patchtest`` to +about patch status. We are looking at improving tools such as ``patchtest`` to test user contributions before they hit the mailing lists and also at better documenting how to use such workflows since we recognise that whilst this was common knowledge a decade ago, it might not be as familiar now. @@ -299,7 +299,7 @@ The Yocto Project uses a `Patchwork instance