From 645d8a927b679a33d6a81aca2ae0ce1be84ad65d Mon Sep 17 00:00:00 2001 From: Trevor Woerner Date: Thu, 18 Sep 2025 17:27:24 -0400 Subject: [PATCH] patchtest.README: trivial fixes Fix two small, trivial issues in the README. Signed-off-by: Trevor Woerner Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie --- scripts/patchtest.README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/patchtest.README b/scripts/patchtest.README index 3c1ee1af1d..1c674e23c9 100644 --- a/scripts/patchtest.README +++ b/scripts/patchtest.README @@ -18,7 +18,7 @@ baseline for development of similar suites for other layers as needed. Patchtest can either run on a host or a guest machine, depending on which environment you prefer. If you plan to test your own patches (a good practice before these are sent to the mailing list), the easiest -way is to install and execute on your local host; in the other hand, if +way is to install and execute on your local host; on the other hand, if automatic testing is intended, the guest method is strongly recommended. The guest method requires the use of the patchtest layer, in addition to the tools available in oe-core: https://git.yoctoproject.org/patchtest/ @@ -33,7 +33,7 @@ by running `pip install -r meta/lib/patchtest/requirements.txt`. Note that git-pw is not automatically added to the user's PATH; by default, it is installed at ~/.local/bin/git-pw. -For git-pw (and therefore scripts such as patchtest-get--series) to work, you need +For git-pw (and therefore scripts such as patchtest-get-series) to work, you need to provide a Patchwork instance in your user's .gitconfig, like so (the project can be specified using the --project argument): -- 2.47.3