diff options
-rw-r--r-- | documentation/contributor-guide/submit-change.rst | 4 |
1 files changed, 2 insertions, 2 deletions
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. | |||
43 | Since we don’t believe that can work for us, the project is aiming to ensure | 43 | Since we don’t believe that can work for us, the project is aiming to ensure |
44 | `patchwork <https://patchwork.yoctoproject.org/>`__ is available to help track | 44 | `patchwork <https://patchwork.yoctoproject.org/>`__ is available to help track |
45 | patch status and also looking at how tooling can provide more feedback to users | 45 | patch status and also looking at how tooling can provide more feedback to users |
46 | about patch status. We are looking at tools such as ``patchtest`` to | 46 | about patch status. We are looking at improving tools such as ``patchtest`` to |
47 | test user contributions before they hit the mailing lists and also at better | 47 | test user contributions before they hit the mailing lists and also at better |
48 | documenting how to use such workflows since we recognise that whilst this was | 48 | documenting how to use such workflows since we recognise that whilst this was |
49 | common knowledge a decade ago, it might not be as familiar now. | 49 | common knowledge a decade ago, it might not be as familiar now. |
@@ -299,7 +299,7 @@ The Yocto Project uses a `Patchwork instance <https://patchwork.yoctoproject.org | |||
299 | to track the status of patches submitted to the various mailing lists and to | 299 | to track the status of patches submitted to the various mailing lists and to |
300 | support automated patch testing. Each submitted patch is checked for common | 300 | support automated patch testing. Each submitted patch is checked for common |
301 | mistakes and deviations from the expected patch format and submitters are | 301 | mistakes and deviations from the expected patch format and submitters are |
302 | notified by patchtest if such mistakes are found. This process helps to | 302 | notified by ``patchtest`` if such mistakes are found. This process helps to |
303 | reduce the burden of patch review on maintainers. | 303 | reduce the burden of patch review on maintainers. |
304 | 304 | ||
305 | .. note:: | 305 | .. note:: |