public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 2/3] RECIPE-API-CHANGELOG: Reorder and capitalize sentences
Date: Thu, 22 Nov 2018 13:58:39 +0100	[thread overview]
Message-ID: <8968a659d794e3488ea8274b02d06980e0063b6d.1542891520.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1542891520.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1542891520.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

Use a consistent chronological order (oldest to newest change) by moving
the upcoming 0.7 changes to the end. Make sentences out of some
statements.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 RECIPE-API-CHANGELOG.md | 68 ++++++++++++++++++++++++-------------------------
 1 file changed, 34 insertions(+), 34 deletions(-)

diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index 7eb5e09..c95c7ac 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -3,40 +3,6 @@ Recipe API Changelog
 
 Baseline: Release v0.5
 
-Upcoming changes (v0.7)
------------------------
-
-### dpkg-raw recipes chown all files to "root:root"
-
-if your recipes rely on any other ownership, you will have to change file
-ownership in the postinst script
-
-### location of image artifacts
-
-Align with OpenEmbedded and place image artifacts in a per-machine folder placed
-in tmp/deploy (to avoid collisions among other things).
-
-### more consistent artifact names
-
-multiconfig image artifacts are all placed in tmp/deploy/images. They include
-kernel, initrd and ext4/wic images. A consistent naming scheme is now used:
-`IMAGE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images
-so no visible changes there. Kernel and initrd images are however affected; for
-instance:
-
-```
-vmlinuz-4.9.0-8-armmp_debian-stretch-qemuarm
-```
-
-is now
-
-```
-isar-image-base-debian-stretch-qemuarm.vmlinuz-4.9.0-8-armmp
-```
-
-It should be noted that the `KERNEL_IMAGE` and `INITRD_IMAGE` variables were
-updated hence recipes using them shouldn't be impacted per se.
-
 Changes in v0.6
 ---------------
 
@@ -106,3 +72,37 @@ reworked and simplified. If your kernel recipe is called `linux-foo_4.18.bb`,
 you now have to set `KERNEL_NAME = "foo"` in order to select that kernel.
 Alternatively, a recipe with a different naming scheme can set
 `KERNEL_NAME_PROVIDED = "foo"` in order to match as well.
+
+Upcoming changes (v0.7)
+-----------------------
+
+### dpkg-raw recipes chown all files to "root:root"
+
+If your recipes rely on any other ownership, you will have to change file
+ownership in the postinst script.
+
+### location of image artifacts
+
+Align with OpenEmbedded and place image artifacts in a per-machine folder placed
+in tmp/deploy (to avoid collisions among other things).
+
+### more consistent artifact names
+
+Multiconfig image artifacts are all placed in tmp/deploy/images. They include
+kernel, initrd and ext4/wic images. A consistent naming scheme is now used:
+`IMAGE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images
+so no visible changes there. Kernel and initrd images are however affected; for
+instance:
+
+```
+vmlinuz-4.9.0-8-armmp_debian-stretch-qemuarm
+```
+
+is now
+
+```
+isar-image-base-debian-stretch-qemuarm.vmlinuz-4.9.0-8-armmp
+```
+
+It should be noted that the `KERNEL_IMAGE` and `INITRD_IMAGE` variables were
+updated hence recipes using them shouldn't be impacted per se.
-- 
2.16.4


  parent reply	other threads:[~2018-11-22 12:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 12:58 [PATCH 0/3] Bitbake fix, kernel-specific package naming Jan Kiszka
2018-11-22 12:58 ` [PATCH 1/3] bitbake: Update to fixed master revision Jan Kiszka
2018-11-22 13:12   ` Henning Schild
2018-11-22 13:14     ` Jan Kiszka
2018-11-22 13:18       ` Henning Schild
2018-11-22 13:25         ` Jan Kiszka
2018-11-22 13:58           ` Henning Schild
2018-11-22 14:28             ` Jan Kiszka
2018-11-22 15:36               ` Henning Schild
2018-11-22 15:42                 ` Jan Kiszka
2018-11-22 13:19       ` Jan Kiszka
2018-11-23 11:27   ` Maxim Yu. Osipov
2018-11-22 12:58 ` Jan Kiszka [this message]
2018-11-22 13:10   ` [PATCH v2 2/3] RECIPE-API-CHANGELOG: Reorder and capitalize sentences Jan Kiszka
2018-11-23 11:28     ` Maxim Yu. Osipov
2018-11-22 12:58 ` [PATCH 3/3] Append KERNEL_NAME to dependent custom modules and u-boot-script Jan Kiszka
2018-11-23 11:28   ` Maxim Yu. Osipov
2018-11-23 11:34     ` Jan Kiszka
2018-11-23 11:38       ` [PATCH v2 " Jan Kiszka
2018-11-23 12:35         ` Maxim Yu. Osipov

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=8968a659d794e3488ea8274b02d06980e0063b6d.1542891520.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --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