From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Megan Knight <megankn@amazon.com>
Subject: [nanbield][PATCH 04/20] dev-manual: layers: update link to YP Compatible form
Date: Mon, 18 Dec 2023 22:33:18 +0100 [thread overview]
Message-ID: <20231218213334.146370-5-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231218213334.146370-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Megan Knight <megankn@amazon.com>
---
documentation/dev-manual/layers.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/dev-manual/layers.rst b/documentation/dev-manual/layers.rst
index c65a94b4fa..b3ccf633df 100644
--- a/documentation/dev-manual/layers.rst
+++ b/documentation/dev-manual/layers.rst
@@ -313,7 +313,7 @@ Logo for your layer and application. The process consists of two parts:
successful compatibility registration.
#. Completion of an application acceptance form, which you can find at
- :yocto_home:`/webform/yocto-project-compatible-registration`.
+ :yocto_home:`/compatible-registration/`.
To be granted permission to use the logo, you need to satisfy the
following:
@@ -337,7 +337,7 @@ application, you can use the Yocto Project Compatibility Logo with your
layer and the application that uses your layer.
To access the form, use this link:
-:yocto_home:`/webform/yocto-project-compatible-registration`.
+:yocto_home:`/compatible-registration`.
Follow the instructions on the form to complete your application.
The application consists of the following sections:
--
2.34.1
next prev parent reply other threads:[~2023-12-18 21:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:33 [nanbield][PATCH 00/20] Documentation backports michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 01/20] migration-guides: release 3.5 is actually 4.0 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 02/20] contributor-guide: fix command option michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 03/20] contributor-guide: add License-Update tag michael.opdenacker
2023-12-18 21:33 ` michael.opdenacker [this message]
2023-12-18 21:33 ` [nanbield][PATCH 05/20] migration-guide: add release notes for 4.2.4 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 06/20] ref-manual: releases.svg: update nanbield release status michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 07/20] manuals: fix URL michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 08/20] migration-guide: add release notes for 4.0.14 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 09/20] ref-manual: Fix reference to MIRRORS/PREMIRRORS defaults michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 10/20] dev-manual: Discourage the use of SRC_URI[md5sum] michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 11/20] test-manual: text and formatting fixes michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 12/20] test-manual: resource updates michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 13/20] test-manual: add links to python unittest michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 14/20] test-manual: explicit or fix file paths michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 15/20] test-manual: add or improve hyperlinks michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 16/20] migration-guides: reword fix in release-notes-4.3.1 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 17/20] manuals: brief-yoctoprojectqs: align variable order with default local.conf michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 18/20] dev-manual: runtime-testing: fix test module name michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 19/20] migration-guides: add release notes for 4.0.15 michael.opdenacker
2023-12-18 21:33 ` [nanbield][PATCH 20/20] test-manual: use working example michael.opdenacker
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=20231218213334.146370-5-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=megankn@amazon.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