From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Trevor Gamblin <tgamblin@baylibre.com>
Subject: [PATCH 2/6] patchtest.README: update name and location or patchtest layer
Date: Thu, 18 Sep 2025 17:27:25 -0400 [thread overview]
Message-ID: <20250918212743.3960-2-twoerner@gmail.com> (raw)
In-Reply-To: <20250918212743.3960-1-twoerner@gmail.com>
The patchtest layer's name and location have changed from:
patchtest
https://git.yoctoproject.org/patchtest
to:
meta-patchtest
https://git.yoctoproject.org/meta-patchtest
Update any references of the old name and repository to the new ones.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
scripts/patchtest.README | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/scripts/patchtest.README b/scripts/patchtest.README
index 1c674e23c9ab..5a9dabc50b44 100644
--- a/scripts/patchtest.README
+++ b/scripts/patchtest.README
@@ -20,8 +20,9 @@ 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; 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/
+The guest method requires the use of the meta-patchtest layer, in
+addition to the tools available in oe-core:
+https://git.yoctoproject.org/meta-patchtest/
## Installation
@@ -43,7 +44,7 @@ To work with patchtest, you should have the following repositories cloned:
1. https://git.openembedded.org/openembedded-core/ (or https://git.yoctoproject.org/poky/)
2. https://git.openembedded.org/bitbake/ (if not using poky)
-3. https://git.yoctoproject.org/patchtest (if using guest mode)
+3. https://git.yoctoproject.org/meta-patchtest (if using guest mode)
## Usage
@@ -98,8 +99,8 @@ from the mailing lists. When executed this way, the test process is
essentially running random code from the internet and could be
catastrophic if malicious bits or even poorly-handled edge cases aren't
protected against. In order to use this mode, the
-https://git.yoctoproject.org/patchtest/ repository must be cloned and
-the meta-patchtest layer added to bblayers.conf.
+https://git.yoctoproject.org/meta-patchtest/ repository must be cloned
+and added to bblayers.conf.
The general flow of guest mode is:
--
2.51.0.193.g4975ec3473b4
next prev parent reply other threads:[~2025-09-18 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 21:27 [PATCH 1/6] patchtest.README: trivial fixes Trevor Woerner
2025-09-18 21:27 ` Trevor Woerner [this message]
2025-09-18 21:27 ` [PATCH 3/6] patchtest.README: update installation instructions Trevor Woerner
2025-09-18 21:27 ` [PATCH 4/6] patchtest.README: expand obtaining patches Trevor Woerner
2025-09-18 21:27 ` [PATCH 5/6] patchtest.README: update host mode section Trevor Woerner
2025-09-18 21:27 ` [PATCH 6/6] patchtest.README: update selftest section Trevor Woerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250918212743.3960-2-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tgamblin@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox