From: Zhihang Wei <wzh@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH] Doc: Fix a duplicated line in RECIPE-API-CHANGELOG.md
Date: Wed, 5 Nov 2025 09:50:38 +0100 [thread overview]
Message-ID: <20251105085038.3302159-1-wzh@ilbers.de> (raw)
A duplicated line was accidentally added to RECIPE-API-CHANGELOG.md when
resolving conflicts. This patch corrects the doc.
Signed-off-by: Zhihang Wei <wzh@ilbers.de>
---
RECIPE-API-CHANGELOG.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index 247aac13..88819993 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -790,14 +790,13 @@ unset (the default), `Rules-Requires-Root` will not be added. Otherwise,
Set `Rules-Requires-Root: no` in `debian/control` files to prevent unnecessary
invocation of fakeroot during package builds. This follows Debian guidelines
recommending not to use fakeroot when no privileged operations (e.g., `chown`,
-root file modifications) are required.
+root file modifications) are required.
### Add opensbi class to simplify custom OpenSBI builds
A new class called `opensbi` has been introduced that shall help writing
shorter recipes for custom OpenSBI builds. Usage examples can be found in
`meta-isar/recipes/bsp/opensbi`.
-root file modifications) are required.
### Populate systemd units based on presets during image postprocessing
--
2.39.5
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20251105085038.3302159-1-wzh%40ilbers.de.
reply other threads:[~2025-11-05 8:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251105085038.3302159-1-wzh@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.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