public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>
To: jan.kiszka@siemens.com, isar-users@googlegroups.com,
	felix.moessbauer@siemens.com
Subject: [PATCH 1/2] Add removal of deb_compat to API changelog.
Date: Wed, 21 Feb 2024 09:42:19 +0100	[thread overview]
Message-ID: <20240221084257.16543-2-Quirin.Gylstorff@siemens.com> (raw)
In-Reply-To: <20240221084257.16543-1-Quirin.Gylstorff@siemens.com>

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

The function deb_compat was replaced with a dependency to
debhelper-compat.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
 RECIPE-API-CHANGELOG.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index bea12871..2da7968d 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -566,3 +566,9 @@ supported, but a warning is issued when it is used. Future versions will drop
 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
+
+Remove all uses of the function deb_compat. The functionality was replaced with
+a dependency to the package debhelper-compat.
+
-- 
2.43.0


  reply	other threads:[~2024-02-21  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  8:42 [PATCH 0/2] Removal of deb_compat Quirin Gylstorff
2024-02-21  8:42 ` Quirin Gylstorff [this message]
2024-02-21  8:42 ` [PATCH 2/2] debianize: add_warning in case deb_compat is used Quirin Gylstorff
2024-02-29 13:18 ` [PATCH 0/2] Removal of deb_compat 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=20240221084257.16543-2-Quirin.Gylstorff@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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