From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] RECIPE-API-CHANGELOG.md: Fix tag
Date: Mon, 29 Apr 2024 17:32:46 +0300 [thread overview]
Message-ID: <20240429143246.388669-1-amikan@ilbers.de> (raw)
We already tagged Isar to v0.10 so update tag in changelog.
Also correct title format.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
RECIPE-API-CHANGELOG.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index fac76357..12ea93ec 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -404,8 +404,8 @@ The user and groups defined by the variables `USERS` and `GROUPS`
was moved from image configuration to image post processing. The users and
groups are now created after all packages are installed.
-Changes in next
----------------
+Changes in v0.10
+----------------
### Buildchroot no longer used for package building
@@ -567,11 +567,14 @@ When building a custom kernel module, the `KBuild` file might be located in
a subdirectory. To support this use-case, set `MODULE_DIR=$(PWD)/subdir` in
the module build recipe.
-### function debianize:deb_compat is removed
+### Function debianize:deb_compat is removed
Remove all uses of the function deb_compat. The functionality was replaced with
a dependency to the package debhelper-compat.
+Changes in next
+---------------
+
### Change OPTEE_BINARIES default ###0
Since OP-TEE 3.21, tee-raw.bin is produced for all platforms and is considered
--
2.34.1
next reply other threads:[~2024-04-29 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 14:32 Anton Mikanovich [this message]
2024-05-06 16:15 ` Uladzimir Bely
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=20240429143246.388669-1-amikan@ilbers.de \
--to=amikan@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